[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [kde] setting an /opt precedent



On Thu, Jan 17, 2002 at 02:44:07PM -0500, Jeff Licquia wrote:
> On Thu, 2002-01-17 at 14:26, Eray Ozkural (exa) wrote:
> > On Thursday 17 January 2002 20:04, Junichi Uekawa wrote:
> > >        Distributions may install software in /opt, but should not modify or
> > >        delete software installed by the local system administrator without
> > > the assent of the local system administrator.
> > >
> > > Tell me how you achieve the above, with Debian packages touching
> > > /opt/kde

> > As explained in section 3.8, it is obvious. Local system administrator, as I 
> > have written, manages the contents of the following directories.
> >   /opt/bin, /opt/doc, /opt/include, /opt/info, /opt/lib, and /opt/man
> >
> > A distribution therefore cannot touch the content of these subdirs, however 
> > it can install software in a package directory
> >   /opt/<package>
> > under which the files pertaining to <package> are maintained. FHS explicity 
> > allows this.

> That is not what the text of the FHS says.  There is no limitation
> mentioned that states that the admin cannot install software outside of
> /opt/bin, etc.  And, wherever in /opt the admin decides to install
> software, packages "should not modify or delete software installed by
> the local system administrator without the assent of the local system
> administrator."  Period.

> We cannot currently ensure that a package installing to /opt cannot
> overwrite admin-installed software there.

Oh, sure we can -- Eray can create his own little packages for KDE3, 
where every single file is a conffile...

Steve Langasek
postmodern programmer

Attachment: pgp8SHLcVTO9u.pgp
Description: PGP signature


Reply to: