On 5/17/2011 6:30 PM, [email protected] wrote:
One hunk of a patch failed because it is now already in trunk. Easy to
fix.
But I'm really not feeling like fixing it if my work isn't going to get
into trunk.
I think having somebody (me) running daily builds of trunk on a small
production server is useful. As well as the increased ease of building
debian packages of releases for other people to more easily test.
And I think the argument that having an updated debian build directory in
trunk is bad because it *might* one day become unmaintained again is crap.
It's not like I'm suggesting an overhaul of some integral SpamAssassin code
that makes it difficult for other people to maintain. It's one isolated
debian directory that can be deleted the instant somebody notices it's not
maintained.
I'm getting emails, on a daily basis, if these daily builds fail. I think
I'm likely to keep up maintenance of the debian build info in trunk. I'll
try to make a point of letting you folks know if I stop.
May I please update the debian directory in trunk, instead of it just being
deleted.
You've stepped up to set you'll do it so I'm willing to give you a shot
and commit a patch for an updated .debian file.
Regards,
KAM
