[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 71318] import existing project: network path not allowed (have to choose a directory)
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-06-24 8:42:31
Message-ID: 20050624084231.21096.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=71318         




------- Additional Comments From richard in-fase nl  2005-06-24 10:42 \
------- I reported a dup of this bug and "Amilcar do Carmo Lucas" commented \
there:

> This is a duplicate.
> 
> And it will probably be closed as wontfix.
> 
> AFAIK the line does not work:
> gcc -c sftp://blabla.com/bla.c
> 
> And unless you "fix" gcc it never will

I can see the point if you use kdevelop only for c/c++ but I'm using \
kdevelop for Perl. We have a development server with apache and mod_perl \
installed on it, with identical setup as the production servers. It's not \
possible to do development on my own box because I use a different \
distribution with different versions of apache, mod_perl, etc. So it would \
be very handy for me to be able to develop directly on the development \
server. 

I think it's not a complex fix because kdevelop supports the sftp:// \
prefixes in the file browser, and it can open existing projects on sftp \
locations.

It can also be an improvement for c++ developers. Of course they have to \
run 'make' on the other computer then. kdevelop can always show a \
warning/error saying something like: "cannot compile project at remote \
location".


[prev in list] [next in list] [prev in thread] [next in thread]