As nobody has yet argued against my policy proposal of adopting the
FHS, it is likely to become policy quite soon. So we need to start
actively thinking about how to go about managing the changeover, and
which exceptions we will make.
A quick think would indicate that the most likely difficulties are to
be found in the /usr/doc -> /usr/share/doc move, especially if
/usr/doc/foo/examples contains compiled binaries.
AFAIK, the /usr/info -> /usr/share/info is well under way, as is
/usr/lib/texmf -> /usr/share/texmf.
The /var/lib/dpkg hierarchy will be an exception to the FHS: it is far
to dangerous at this stage even to consider moving it to
/var/state/dpkg (although what will happen when we move to DPKGv2 is
anyone's guess).
So it would be very good to hear from people: what problems are we
likely to face in the move, how can we do it without destroying 2500+
packages, etc., etc.
And we should do this sooner rather than later, as otherwise it will
very adversely affect the potato freeze.
We may need some mass NMU's, but it would be nice if that could be
avoided.
Julian
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer. [EMAIL PROTECTED]
-*- Finger [EMAIL PROTECTED] for my PGP public key. -*-
