Previously Jarno Elonen wrote:
> * Many people feel that KDE (and Gnome) is too large
>a whole to be stuffed in /usr/bin, /usr/share etc
>and would deserve a separate directory like X
Define many. I also don't see what the advantage would be of moving
it to a seperate directory. Without k
hi :)
On Wed, Jan 16, 2002 at 02:25:36PM -0600, David Starner wrote:
> If a package source does not come fully unpacked - i.e. it uses a
> DBS-like system - debian/rules must include an unpack target, that
> unpacks the source code and applies all patches to it.
i think this is the wrong approach
On Wed, Jan 16, 2002 at 11:19:25PM +0200, Jarno Elonen wrote:
> Hi,
>
> May I try to summarize the filesystem discussion on KDE list and suggest that
> it will continue in debian-policy?
>
> * Many people feel that KDE (and Gnome) is too large
>a whole to be stuffed in /usr/bin, /usr/share
On Wed, Jan 16, 2002 at 02:25:36PM -0600, David Starner wrote:
> If a package source does not come fully unpacked - i.e. it uses a
> DBS-like system - debian/rules must include an unpack target, that
> unpacks the source code and applies all patches to it.
Make it another optional target listed in
Jarno Elonen <[EMAIL PROTECTED]> cum veritate scripsit:
> Does it make any sense? I.e. have I missed some important aspect of Unix
> here?
I think you are going backwards in time somewhat.
That's the past, and the current trend is to move away from such setup,
and some people thought it is even
Hi - again,
I already requested comments for the following filesystem layout on the KDE
list but I guess this list is a bit more appropriate for the subject.
Now that I've thought a bit more about it, I think this possibly could work
with ordinary symlinks, too, and moving to the new layout wou
Hi,
May I try to summarize the filesystem discussion on KDE list and suggest that
it will continue in debian-policy?
* Many people feel that KDE (and Gnome) is too large
a whole to be stuffed in /usr/bin, /usr/share etc
and would deserve a separate directory like X
* Some proposed using
A suggestion for policy:
If a package source does not come fully unpacked - i.e. it uses a
DBS-like system - debian/rules must include an unpack target, that
unpacks the source code and applies all patches to it.
The motivation is, that I'm tired of wanting to look at the source code
to a program
See www.apocketfullofeuros.com for an
unofficial guide to EU R&D framework
funding
9 matches
Mail list logo
