Re: DAK (2)
Brian May <email@example.com> writes:
> On Wed, Dec 11, 2002 at 01:11:08AM +0000, James Troup wrote:
> > Err, bullshit, there's doc/*.1.sgml and --help for most of the key
> > scripts.
>  [snoopy:unstable:bam] ~/cvswork/dak >helena --help
helena is not a key script. Try again. grep -lir 'Options\["help"\]' dak shows:
amber, catherine, claire.py, charisma, fernanda.py, halle, heidi,
jenna, jennifer, jeri, julia, lisa, kelly, madison, melanie, rhona,
All at least recognise help and that is IMNSHO more than most of the
key scripts (and several less-than-key ones).
> This seems to be common for all the programs I have tried so far.
Sorry, don't believe you. See above.
> How do you change it?
Dinstall::OverrideMaintainer - see katie.conf.security.
> Is it possible to just have it mail the uploader?
No because in the Debian world (which includes queue daemons and
buildds) it's not possible to sanely determine who the human uploader
is. It'd be trivial to add if there was such a way in your
> errr.... I don't consider this to be Debian packaging:
> katie (0notforuse0-0) unstable; urgency=low
> * Initial non-release. [The packaging is nowhere near complete; don't
> * bother trying to use it unaltered.]
> -- James Troup <firstname.lastname@example.org> Tue, 25 Sep 2001 22:59:17 +0100
> If this actually has been tested and does generate a valid package,
> I stand corrected; but this comment makes it look like it never
> has been tested.
I find it strange that you take some comments (like the above) at more
than there face value, yet can't even parse seemingly
easier-to-understand comments like the one in cron.weekly.
There is packaging; it produces a deb, but it's not perfect and so
there's a disclaimer in there. And sorry but I still think you didn't