[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: new approach: Documentation Policy

>  > > Can't deity be implemented to match something like
>  > >
>  > >         /usr/doc/*/html
>  > >
>  > > too? I wouldn't like to "centralize" documentation again. (We already had
>  > > /usr/doc/copyright and /usr/doc/examples, but they have been removed.)
>  >
>  > Probably, yes.  The original design only called for prefixes because it
>  > also allowed replacements -- changing the prefix so someone could do
>  > something like move all man pages from /usr/man to /usr/share/man.
>  >
>  > Such replacements is much more difficult to implement when you can have
>  > wildcards anywhere in the path.
> What about using a sed-like mechanism (I mean, in s/.../.../
> commands) allowing rules as "/usr/doc/examples/\1 ->
> /usr/doc/\(.*\)/examples".

It's possible, but probably not worth it.  It has to be simple enough
for anyone to use and regexp is not for beginners.

> BTW allowing such rules to be set up at any time after package
> installation would provide a mechanism to "locally fix" packages using
> an old version of the policy, without systematically re-downloading
> them (in case just the layout has changed).

That's possible, but can also be accomplished with "rm <whatever>" or
"mv <whatever>" in almost all cases.

                                 ( bcwhite@verisim.com )

 Generated by Signify v1.02.  For this and more, visit http://www.verisim.com/

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: