patching CPAN bugs (was Re: [siesta-dev] and again for the archives)

[prev] [thread] [next] [lurker] [Date index for 2003/04/04]

From: Nicholas Clark
Subject: patching CPAN bugs (was Re: [siesta-dev] and again for the archives)
Date: 13:13 on 04 Apr 2003
On Fri, Apr 04, 2003 at 12:45:17PM +0100, Richard Clamp wrote:
> On Fri, Apr 04, 2003 at 11:01:24AM +0100, Simon Wistow wrote:
> > On Fri, Apr 04, 2003 at 10:44:32AM +0100, Richard Clamp said:
> > > Bugs in Email::LocalDelivery::Maildir meant no archiving was
> > > working.  I'll therefore be playing back commitmails again.  Joy.
> > 
> > Was it the hacking I did or just fundamental bugs?
> Fundamentals.   This is the fix I've applied locally (blowing away
> your changes) 
> Now it's just a case of waiting for a new release so we can update the
> Build.PL.

I presume that these things we're finding in modules we use are at best
irritants, and at worst showstopper bugs that halt ongoing development?

So to allow ongoing development while we've reported bugs but the upstream
author isn't doing things, I think that we probably ought to have some sort
of version control on local hacks

I'm envisaging importing the source of any module when we find a need to
change it, and keeping any local hacks under source control. This way
anything we install is either vanilla third party releases, or something
we can replicate from source control.

I'm not sure how easy it is to unimport something (or re-import it) when
the upstream package has a new release. Maybe we don't - maybe we import
the whole directory (say Foo-0.03) and when Foo 0.04 is release we commit
a delete on Foo-0.03 and run with clean 0.04, only importing Foo-0.04 later
if we find a new bug in it.

There's stuff above here

Generated at 13:56 on 01 Jul 2004 by mariachi 0.52