Re: Interpreting FHS

2002-01-17 Thread Daniel Stone
On Thu, Jan 17, 2002 at 03:45:40PM +0200, Eray Ozkural (exa) wrote: > On Thursday 17 January 2002 07:22, Daniel Stone wrote: > > > Now is a good time to follow wisdom of KDE hackers and install it in > > > /opt/kde3 as we should. So that we don't have all of KDE cluttering the > > > whole filesyste

Re: Interpreting FHS

2002-01-17 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 17 January 2002 07:22, Daniel Stone wrote: > > Now is a good time to follow wisdom of KDE hackers and install it in > > /opt/kde3 as we should. So that we don't have all of KDE cluttering the > > whole filesystem namespace (such as /usr/sha

Re: Interpreting FHS

2002-01-17 Thread Jarno Elonen
> True, but putting the packages directly under /usr is so "flat", > and makes it impossible to put them on another partition. Maybe > /usr/packages would be a better place, to (a) keep it under /usr, > and (b) be able to mount it in a different partition. Maybe a structure like this... + usr

Re: Interpreting FHS

2002-01-16 Thread Daniel Stone
On Wed, Jan 16, 2002 at 08:25:15PM +0200, Eray Ozkural (exa) wrote: > On Wednesday 16 January 2002 16:53, Hendrik Sattler wrote: > > > > But kde in /opt is sick. You cannot say: > > this app is an KDE2 app, so install it in /opt/kde2 > > > > This way, you do not look at packages which are somewhat

Re: Interpreting FHS

2002-01-16 Thread Daniel Stone
On Wed, Jan 16, 2002 at 04:18:49PM +0200, Eray Ozkural (exa) wrote: > On Wednesday 16 January 2002 13:24, Daniel Stone wrote: > > > > I will not, under any circumstances, touch /opt. I believe Debian policy > > prohibits it anyway. > > I read the complete section for opt in the FHS. Here is my ana

Re: Interpreting FHS

2002-01-16 Thread Ron Johnson
On Wed, 16 Jan 2002 20:05:00 -0600 Chris Cheney <[EMAIL PROTECTED]> wrote: > On Wed, Jan 16, 2002 at 07:40:26PM -0600, Ron Johnson wrote: > > Call me crazy, but I've always thought that soft symlinks could be great > > here: > > - Put each package in it's own subdir under, say, /pkg. > > - Next, p

Re: Interpreting FHS

2002-01-16 Thread Chris Cheney
On Wed, Jan 16, 2002 at 07:40:26PM -0600, Ron Johnson wrote: > Call me crazy, but I've always thought that soft symlinks could be great here: > - Put each package in it's own subdir under, say, /pkg. > - Next, put symlinks into /usr/bin, /usr/lib, /etc, ad nauseum, in order to > follow the Debian

Re: Interpreting FHS

2002-01-16 Thread Ron Johnson
Call me crazy, but I've always thought that soft symlinks could be great here: - Put each package in it's own subdir under, say, /pkg. - Next, put symlinks into /usr/bin, /usr/lib, /etc, ad nauseum, in order to follow the Debian Policy. This way, you could have /pkg/qt2, /pkg/qt3, /pkg/kde2, etc.

Re: Interpreting FHS

2002-01-16 Thread Chris Cheney
On Thu, Jan 17, 2002 at 02:48:06AM +0200, Jarno Elonen wrote: -snip- > If there were a way to remove symlinks when the original file is removed, > I think the following structure would be the easiest to understand and > administrate: > > + usr > + bin > + qtcups -> ../qtcups/bin/qtcups

Re: Interpreting FHS

2002-01-16 Thread ben
On Wednesday 16 January 2002 12:20 pm, Jarno Elonen wrote: [snip] > That said, FHS hardly is, if I have understood correctly, "the optimal > solution" for anything but rather an educated tradeoff between usefulness > and compatibility with existing UNIX systems. People generally present > crique be

Re: Interpreting FHS

2002-01-16 Thread David Bishop
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 January 2002 02:06 pm, Eray Ozkural (exa) wrote: > On Wednesday 16 January 2002 20:25, Eray Ozkural (exa) wrote: > > up just in debian. And may I add that KDE hackers loathe the debian > > packaging somehow? [*] There is some major misu

Re: Interpreting FHS

2002-01-16 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 January 2002 20:25, Eray Ozkural (exa) wrote: > up just in debian. And may I add that KDE hackers loathe the debian > packaging somehow? [*] There is some major misunderstanding there, some [*] This is my impression from conversations

Re: Interpreting FHS

2002-01-16 Thread Jarno Elonen
On Wednesday 16. Januaryta 2002 20:27, Eray Ozkural (exa) wrote: > On Wednesday 16 January 2002 17:41, Hendrik Sattler wrote: > > The problem: where to install libs that come with the package and other > > might refer to? How to search for installed programs by looking at one > > direcory (without

What's really missing ;) (WAS: Re: Interpreting FHS)

2002-01-16 Thread Achim Bohnet
Hi, FWIW and only IMHO: I like that the layout used for KDE is the same as the rest of Debian. Nevertheless I agree that there is a 'big' problem with KDE in Debian KDE is configured to put config files to /etc/kde2 but KDE nevertheless uses /usr/share/config during runti

Re: Interpreting FHS

2002-01-16 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 January 2002 17:41, Hendrik Sattler wrote: > > The problem: where to install libs that come with the package and other > might refer to? How to search for installed programs by looking at one > direcory (without masses of symlinks)? How

Re: Interpreting FHS

2002-01-16 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 January 2002 16:53, Hendrik Sattler wrote: > > But kde in /opt is sick. You cannot say: > this app is an KDE2 app, so install it in /opt/kde2 > > This way, you do not look at packages which are somewhat KDE2 but not > completely (e.g. l

Re: Interpreting FHS

2002-01-16 Thread Jarno Elonen
> > Just as a side note (NOT as a proposition by any means!): > > what's really so wrong in C:\program files style? Of course, on > > open systems, instead of vendor specific directories, there should be some > > other subdirectory policy (lsm for example?). > > The problem: where to install libs

Re: Interpreting FHS

2002-01-16 Thread Hendrik Sattler
Am Donnerstag, 17. Januar 2002 01:48 schrieb Jarno Elonen: > > In my understanding: /opt is for packages that do not fit into the unix > > file system structure with the defined dirs like bin, lib, etc. > > What you now want to do with /opt is to make it to something like > > C:\programs on Windows

Re: Interpreting FHS and KDE filesystem structure

2002-01-16 Thread James Thorniley
definitely would be against FHS. However I agree it would be better than /opt/kde3, especially if we take note of Mark Brown's argument (from Re: Interpreting FHS): > Deciding to use it [/opt] for KDE would, however, result in large numbers of > admins becoming more than a little grump

Re: Interpreting FHS

2002-01-16 Thread Jarno Elonen
> In my understanding: /opt is for packages that do not fit into the unix file > system structure with the defined dirs like bin, lib, etc. > What you now want to do with /opt is to make it to something like C:\programs > on Windows systems. Just as a side note (NOT as a proposition by any means

Re: Interpreting FHS

2002-01-16 Thread Hendrik Sattler
Am Mittwoch, 16. Januar 2002 15:18 schrieb Eray Ozkural (exa): > As I said, there is absolutely nothing in the FHS or Debian Policy that > prohibits installing KDE in /opt. We need to interpret FHS correctly. KDE > is an application package (a rather big one, though) and it would not be > incorrect

Re: Interpreting FHS

2002-01-16 Thread Mark Brown
On Wed, Jan 16, 2002 at 04:18:49PM +0200, Eray Ozkural (exa) wrote: > Using /opt for packages doesn't violate the policy in any way. I repeat, > James *is* right. I suggest you to read it thoroughly before making further > judgement. Deciding to use it for KDE would, however, result in large nu

Interpreting FHS

2002-01-16 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 January 2002 13:24, Daniel Stone wrote: > > I will not, under any circumstances, touch /opt. I believe Debian policy > prohibits it anyway. I read the complete section for opt in the FHS. Here is my analysis. Using /opt for packages d