Bruce Dubbs wrote these words on 10/30/05 22:48 CST:
> The purpose of the /opt/kde methodology is to keep *all* the kde system
> files in one subtree. Then, if a user creates multiple versions,
> *everything* can be changed with a single symlink. Right now I have
> kde-3.4.{0,1,2,3} all in /opt and can easily compare versions with a
> logout; ln -sfn <version>; startx.
But /opt/kde/etc is not FHS compliant. Simply passing
--sysconfdir=/etc/kde-$KDE-VERSION would do the same thing and
provide FHS compliancy. I *almost* went that way with GNOME this
time around, but didn't want to rock the boat.
I now use /etc/gnome-2.12.x as a sysconfdir, in case I want to
update GNOME on the partition. I should have gone with my instincts
and done it that way in the book, but feel I'm still too new of an
editor to make such a radical change to the BLFS book.
Getting back to your idea that everything in /opt/kde keeps
everything central is a good idea, but it is *not* FHS compliant.
I can't stress this enough. Especially for folks that put KDE
in /usr. However, moving the sysconfidir to a unique dir in /etc/
accomplishes the same thing (providing centralized unique files to
a version of KDE) while still affording FHS compliancy.
To me it is a no-brainer. This is why I brought up the issue. We
need to provide instructions that work for each of the methods that
we propose, be it /usr or /opt/kde. Making the sysconfdir to /etc
works always. Why not do it that way?
--
Randy
rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
22:53:01 up 36 days, 8:17, 3 users, load average: 0.04, 0.11, 0.17
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
