[Bug 60067] Automake, configure, make, install dependancies

[Sphere]

------- 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=60067     




------- Additional Comments From sphere1952 at attbi.com  2003-06-19 21:43 -------
Subject: Re:  Automake, configure, make, install dependancies

Jonas Jacobi wrote:

>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
>     
>http://bugs.kde.org/show_bug.cgi?id=60067     
>
>
>
>
>------- Additional Comments From j.jacobi at gmx.de  2003-06-19 19:26 -------
>  
>
>>If that were correct then when I built a test project and tried to run it  
>>without installing it first I would have been told that I hadn't  
>>installed it.  
>>    
>>
>I assume you are alluding to your kpart and my hint to install it. There is the necessity 
>to install it (at least afaik), 'cause the klibloader searches for the kpartlib in the kde/lib 
>directory (maybe there is a way to provide other paths to it). For convenience during 
>development of a kpart, just symlink the kpartlib(no need for the "shell"-binary) to your 
>project path, so you don't have to install every time. Maybe there are nicer solutions, 
>that's just the way i do it. 
>Yours, 
>Jonas
>
>  
>
The problem with that is that it pollutes the file space.  It's putting
work-in-progress into the production area which is the problem.
If you've got a couple of thousand employees and you have to keep
their data backed up every night you're going to keep their files on
a fileserver, not their PC.  That means that everyone will be using
the same copy of KDE, and the same directory tree.  You're proposing
that the programmers install their toys into the same KDE the
secretaries are using.  (And just how many programs named "test"
are there in the world anyway?)