Bug#40706: usr/share/doc vs. /usr/doc
On Wed, 07 Jul 1999, Santiago Vila wrote:
> > With this we have the following four stages:
> For people not using helper tools (there are many of them), this
> means *double* work for every package, because you have first to
> provide symlinks and then you have to remove them.
>
> I do not think it is reasonable.
I see the problem, but I don't see an alternative proposal.
Do you think that all packages will be converted to FHS before
releasing potato? This is my preferred solution, but I don't think
that it is really possible to convert all packages for all
architectures soon.
> The FHS migration will be painful enough so that we have to make it
> twice. Better to do it at a time (on a per package basis), only
> *once*.
I prefer some pain to us developers in contrast to the pain to the
users who have to search for every single package documentation, if we
use two directories for this in parallel.
> I would much prefer some sort of "light" release goal (i.e. not to
> be interpreted very strictly). For example: "We will try to make all
> base and priority >= standard packages in potato to use
> /usr/share/doc instead of /usr/doc".
This doesn't really help the user searching for documentation. He
still has to search both directories for the documentation, if he
doesn't know which packages are priority >= standard (I personally
don't know this for most packages).
I prefer a release "light" goal, like this: "Every package
documentation can be accessed as /XXX/<package>" (where XXX is a
constant for _all_ packages). This was true for slink and I think it
should be true for potato, too. Otherwise potato will be worse than
slink and IMHO we shouldn't step back...
Ciao
Roland
--
* roland@spinnaker.de * http://www.spinnaker.de/ *
PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF
Reply to: