Proposal for KDE 4.0
Richard Smith
kde at metafoo.co.uk
Wed Aug 18 14:45:34 BST 2004
On Wednesday 18 August 2004 1:49 pm, Allan Sandfeld Jensen wrote:
> On Wednesday 18 August 2004 13:42, Stephan Kulow wrote:
> > Am Mittwoch 18 August 2004 11:51 schrieb Adrian Schroeter:
> > > > Now only imagine if we could convince *all* distributors that
> > > > /usr/kde4 is the right $KDEDIR for KDE 4. *gasp* I guess I should
> > > > start with SUSE ;-) (Coolo, Adrian, are you listening?)
> > >
> > > The current plan is to move directly to /usr for KDE 4. But maybe
> > > /usr/kde4 is a better idea. However, we will place it everywhere, if it
> > > is okay with the FHS and there is any official recommendation by KDE ;)
> >
> > /usr/kde4 is _not_ FHS compliant - $KDEDIR is dead, did I tell you?
>
> /usr/X11R6 has an expection. I say we make /usr/kde4 FHS compliant by
> making another exception.
The FHS says:
"Large software packages must not use a direct subdirectory under the /usr
hierarchy."
That seems pretty clear to me. But more to the point: why would you want to
have a /usr/kde4?
Here's why I don't: some sysadmins like to do sane things with /usr/share
(like sharing it across machines with different architectures), and you're
suggesting stopping them. Plus, already, any C or C++ library package you
care to include puts its headers in /usr/include/package,
or /usr/include/package<version> if you're lucky. Why should we break this
trend? I can see it causing only confusion.
Richard
More information about the kde-core-devel
mailing list