Hi,
>>"Anthony" == Anthony Towns <aj@azure.humbug.org.au> writes:
Anthony> Then those packages are welcome to stay in /usr/doc, if
Anthony> complying with the transition strategy irks the maintainer
Anthony> too much. When policy changes, they'll just have to be
Anthony> prepared to move more or less immediately, without as much
Anthony> time for debugging as everyone else had.
I guess I am confused about this now. How can policy change
suddenly, since it makes other packages buggy? Does this mean the
tech ctte has to get involved? How many packages is it OK for policy
to ``suddenly make buggy''?
Is a policy that merely codifies existing practice worth
having?
And is the current reading that the -policy mailing list has
no authority to change policy, so this mailing list is now defunct?
Also: To whom does the tech ctte answer? Seems to me that once
constituted, the ctte is a law unto itself, voting in new members as
they please.
manoj
not back yet
--
"We wish to suggest a structure for the salt of deoxyribose nucleic
acid (D.N.A.). This structure has novel features which are of
considerable biological interest." Watson and Crick, 1953
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
