Re: [Module::Build] Fwd: Module::Build integration with revision control and other goodies I need

[Nadim K. <na...@kh...>]

On Sunday 02 April 2006 07.27, Dr Bean wrote:
> On Sat, 01 Apr 2006, Nadim Khemir wrote:
> > - integrating M::B with one's version control tool (version number,
> > CHANGES, ...)
>
> I have often wanted to ask that question here. Originally, they
> were separate in my mind. I was developing using version control
> and then bringing in M::B to publish it.
>
> Then I thought about how they should be integrated, and now I am
> mostly using module-starter --mb, before doing any development at
> all and throwing the whole lot into a repository, even though
> that means working 3 or 4 directories deep in lib.
>
> My latest project, however, I am using 'sudo ./Build install'
> with every hack, because the development is spread out over my
> home directory, and being lax about committing. I haven't been
> doing any committing at all.
 May I ask why you aren't committing anything?

A first thing would be to list what we use for version control and what we 
want to achieve. I'll tell my story and hope other will add their.

I use SVK (though it has seriously upset me lately) and here are the things 
I'd like to do (no particular order):

-when I do a 'dist', I want a CHANGES to be generated automatically

- I want the version to be major.minor.revision and I want that to be 
automatic of course

- The MANIFEST couls also be automatically extracted from what I check in.

- The dependencies  my modules have shouldn't have to be explicitely written 
but extracted

- commit shouldn't (must not?) be allowed if testing fails.

this is what I can think about for the revision control/M::B interaction but 
there might be other goodies to find.

Nadim.