Re: Debian conflicts with FHS on /usr/include/{linux,asm}
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joel Klecker <jk@espy.org> writes:
> At 11:48 -0400 1999-07-09, Kyle Rose wrote:
> >FWIW, everyone I know who uses Debian -- including myself -- changes
> >/usr/include/{asm,linux,scsi} to links as one of the first steps after
> >installation.
>
> Do you realize that /usr/include/scsi belongs to glibc?
I never noticed a problem, since I don't have any SCSI devices. My
mistake. Statement still applies to {asm,linux}, though.
> As far as I'm concerned (as glibc maintainer), if you make such
> changes, you deserve no support from me.
The point is, we shouldn't have to do this. Symlinks may be hell for
dpkg, but it's the way every other distribution has done it since at
least 1994, when I started out with Slackware. I suppose a good
argument for using directories is
(1) Experts who compile their own experimental kernels will make their
own links and throw out the directories
(2) Novices won't know the difference, since they will only compile
stable kernels that have been out long enough for there to exist a
.deb for them.
I suppose this is valid in most cases, but occasionally even a novice
will want to install an improper kernel. What then?
I honestly think a better solution would be to have the links created
at startup to point to the headers of the correct kernel, as in the
following code. (Pardon if the following doesn't work exactly,
because I've never used any of the kernel-source packages.)
test -L /usr/src/linux && (rm -f /usr/src/linux && ln -s linux-`uname
- -r` /usr/src/linux)
This works well with my setup (I keep different kernel sources around
with the names linux-x.y.z), although it does require one to reboot or
knowingly run the script before compiling something for a different
kernel version. Nonetheless, this would remove 99% of the problems
people have when, in their ignorance of Debian's "unique" policy, they
compile a problem to the wrong kernel interface.
I see this as a good way to accomodate both people who get their own
kernel sources, and people who like to download theirs packaged. The
package maintainers can then just install the kernel headers to the
proper place in /usr/src/linux-x.y.z/include/{linux,asm} if the user
doesn't want the entire source installed.
> As for FHS, it is wrong plain and simple.
Then get FHS to change, or live with their policy. Otherwise, Debian
will never be FHS-compliant, plain and simple. It could be that being
FHS-compliant isn't important, but I don't think that's the case.
Kyle
- --
Kyle R. Rose "They can try to bind our arms,
Laboratory for Computer Science But they cannot chain our minds
MIT NE43-309, 617-253-5883 or hearts..."
http://web.mit.edu/krr/www/ Stratovarius
krose@theory.lcs.mit.edu Forever Free
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3hko666jzSko6g9wRAhhgAKDg/ETv52EL6liRCJLIJyzkPQ1b4wCgnstb
+x3Lb3mwgvm4DE8XxF3fOVc=
=GY+n
-----END PGP SIGNATURE-----
Reply to: