Re: Packaging Manual vs. dpkg Programmers' Manual

Hi, >>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes: Ian> However, the erstwhile dpkg programmers' manual was exactly what it Ian> said: it was the documentation for dpkg and dselect. It described how Ian> the programs worked and how they should be used, rather than how to Ian> produce a De

Re: Bug#30036: debian-policy could include emacs policy

Hi, >>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes: Ian> Joey Hess writes ("Bug#30036: debian-policy could include emacs policy"): Ian> ... >> I think we should move the menu hierarchy out of the menu documentation and >> into policy. It is something that could benefit from being maintained

Re: Bug#30036: debian-policy could include emacs policy

Hi, [Sorry for the long delay; real life has a tendency to obtrude] >>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes: Ian> Manoj Srivastava writes ("Re: Bug#30036: debian-policy could include emacs policy"): Ian> ... >> Straw man. No one has said anything about dictating how >> progr

Re: Bug#33156: debian-policy: Cannot find referenced file in given URL

Hamish Moffatt wrote: > Then why are perl scripts allowed? :-) You can easily write some > truely obfuscated perl scripts No you can't; perl is always clear and easily comprehensible! -- #!/usr/bin/perl -i=-/*/~%*~%/~~%/~~~-/*/_/=~~~-/~~! [EMAIL PROTECTED] $o=35;$_="$^I-*!=_!/";s/~/!*/