Re: More FHS stuff
Julian Gilbey wrote:
> > >In other words, is it OK to announce the move to FHS on
> > >-devel-announce so that developers can start making the necessary
> > >changes to their packages?
> > We should wait for FHS 2.1, some of the changes in 2.0 like /var/state
> > will be removed.
>
> My feeling is that this will take a large amount of effort by all of
> the developers, and that the sooner we start, the better, for it will
> definitely hold up the freeze.
No, we can release with this move only partly done. We don't really have
a choice -- I don't think it's something that can be completed in less
than a year.
We'll have to be able to deal with a mix of /usr/doc and /usr/share/doc.
If we can't, then I suggest delaying that aspect until the release after
potato, and making this support a release goal for potato.
(With "deal with" I refer to packages that present /usr/doc to the user,
or otherwise extract information from it.)
> Should we, however, wait for policy version 3.0.0.0 to be released
> officially by Manoj before we announce?
Definitely. Converting a proposal to actual text can turn up all kinds of
snags. It's like waiting for a package to be installed in the archive.
Richard Braakman
Reply to: