>>"Julian" == Julian Gilbey <[EMAIL PROTECTED]> writes:
Julian> People *used* to make that complaint. And if we now move to having a
Julian> lean policy standards document and a developers reference and a best
Julian> programming advice document and a dpkg documentation document, we'll
Julian> have even more complaints in that direction.
I beg to differ. The reason people used to complain was there
was no single place one could go to to get a definitive reference for
all the things a package maintainer _must_ do in order to achieve
interoperability and prevent bug reports.
In the new scheme of things, the policy manual would be the
place to look at. For further assistance, one could look at the
developers reference (HOWTO), the dpkg docs (manual pages for the
tools, references), or the style guide (for tips and solutions). There
is a well defined destination, depending on what one is looking for.
This is a far cry from the old muddle and multiple locations
for must do things we had in the past.
manoj
--
Everything might be different in the present if only one thing had
been different in the past.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
