On Thu, Sep 22, 2005 at 04:39:34PM -0500, Manoj Srivastava wrote: > 4)==
> Added optional dirs /etc/sgml and /etc/xml. The number of mandatory > files in /etc has dropped. (We comply). It does, however, seem to say > we need /etc/X11/XF86Config instead of our XF86Config-4, and want > /etc/X11/Xmodmap (optional, thank goodness). > /etc/X11/xorg.conf seems not to be covered > ********************************NOT COMPLIANT************* Actually, there is no longer an xserver-xfree86 package package in etch, and the xserver-xorg package uses /etc/X11/xorg.conf. That indicates to me that etch is compliant. > 5)== > User specific configuration files for applications are stored in the user's > home directory in a file that starts with the '.' character (a "dot file"). If > an application needs to create more than one dot file then they should be > placed in a subdirectory with a name starting with a '.' character, (a "dot > directory"). In this case the configuration files should not start with the > '.' > character. > This is a new requirement. While moving the configuration > files for various programs may seem like a good idea -- when > these programs were being written. It doesn't seem at all > worthwhile to endure a transition of existing software for the > marginal aesthetic benefits. After all, You have to take into > account to that ~/ is not unusually a shared resource, and the > rest of the world has not changed. Agreed. > ********************************NOT COMPLIANT************** > But this is optional, really. Yep. > 8)== > Requires amd64 to use /lib64 for 64 bit binaries. > I'm told this is not present in our amd64 architecture. I suspect this > > is overspecified in the FHS and policy should excempt ia64 from the > > requirement, although someone should make sure /lib64 works if a > > extra-Debian source puts a library there. > Given that this is an area where standards are actively undergoing revision (i.e., multiarch), I think we should be prepared to diverge from the FHS on this point. > 12)== > Requires boot loader configs in /etc, but does allow them to just be > symlinks to the real location (ie, /etc/grub/menu.lst -> > > /boot/grub/menu.lst). We do not have such symlinks for at least grub, > > didn't check ia64, powerpc, sparc, and other arches that have > > bootloader config files. We will need to fix this. > Alpha definitely needs some improvements to its bootloader setup on new installs; an /etc/ symlink can reasonably be added in the process. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
