module-build-general

[Module-build-general] Re: build and manifest

[Dave R. <au...@ur...>]

[ reply sent to m-b list ... ]

On Mon, 18 Nov 2002, Uri Guttman wrote:

> my first question is about manifest handling. the current method i use
> in stem is actually to tar up what is in CVS. this is good in that i can
> control which files in my dev tree are worth shipping. but it also means
> it ships CVS dirs, and cvs is a pain to manage for manifests. but from
> what i gather with your system, you build MANIFEST from the lib/ dir and
> use the manifest.skip file to control it. i would like to have a
> positive manifest file that i can edit (in addition or whatever). the
> reason is that i have many temp and work in progress files in my dev
> directory and i don't want to have to add each one to the skip
> file. whereas i don't add new source files as frequently so editing a
> manifest.in would be easier for me. this could take dirs and recurse
> down them as well. so any answers or thoughts on a postive manifest.in
> file?

I'll answer this.  BTW, Uri, there's a module-build users list at

For a MANIFEST file, M::B works like EU::MM.  You can provide it a file or
ask it make one for you with "./Build manifest".  Both EU::MM and M::B use
ExtUtils::Manifest under the hood, so the results are pretty much the
same.

The easiest thing to do is let M::B build an initial MANIFEST file, edit
it, and then check it in to CVS.


-dave

/*==================
www.urth.org
we await the New Sun
==================*/

[Module-build-general] Re: build and manifest

[Ken W. <ke...@ma...>]

[cc'd to the module-build list]

Hi Uri,

On Tuesday, November 19, 2002, at 06:52  AM, Uri Guttman wrote:
> hi ken (and dave),
>
> dave is forcing me to use your module::build stuff so i have 
> rtfm'ed and
> will be playing with it more. i have lots of needs and ideas so i feel
> you should get an earful right away. :)

Good, it's always good to have more people trying to do new 
stuff with it.

> my first question is about manifest handling. the current method i use
> in stem is actually to tar up what is in CVS. this is good in 
> that i can
> control which files in my dev tree are worth shipping. but it 
> also means
> it ships CVS dirs, and cvs is a pain to manage for manifests. but from
> what i gather with your system, you build MANIFEST from the 
> lib/ dir and
> use the manifest.skip file to control it. i would like to have a
> positive manifest file that i can edit (in addition or whatever). the
> reason is that i have many temp and work in progress files in my dev
> directory and i don't want to have to add each one to the skip
> file. whereas i don't add new source files as frequently so editing a
> manifest.in would be easier for me. this could take dirs and recurse
> down them as well. so any answers or thoughts on a postive manifest.in
> file?

Module::Build uses the same MANIFEST model as 
ExtUtils::MakeMaker - it uses a MANIFEST file to determine what 
should go in the distribution during 'Build dist' (and 'Build 
disttest', etc.).  You can maintain this MANIFEST file by hand, 
or it will auto-generate it if you do a 'Build manifest'.

So your hand-maintained MANIFEST should work just fine if I 
understand your needs.

> i do appreciate your conceit that who needs make? one day when i have
> mucho money to hire some good hackers, i will lead the creation of my
> super make that will be DB backed, have bidirectional dependency
> knowledge at all times, and have real knowledge about how to 
> build stuff
> instead of annoying templates and macros. i can dream. :)

Heh - I hope I didn't open a can of worms with this M::B 
project, though sometimes it seems as if I did. ;-)

  -Ken

Re: [Module-build-general] Re: build and manifest

[Brian I. <in...@tt...>]

On 19/11/02 10:59 +1100, Ken Williams wrote:
> [cc'd to the module-build list]
> 
> Hi Uri,
> 
> On Tuesday, November 19, 2002, at 06:52  AM, Uri Guttman wrote:
> > hi ken (and dave),
> >
> > dave is forcing me to use your module::build stuff so i have 
> > rtfm'ed and
> > will be playing with it more. i have lots of needs and ideas so i feel
> > you should get an earful right away. :)
> 
> Good, it's always good to have more people trying to do new 
> stuff with it.
> 
> > my first question is about manifest handling. the current method i use
> > in stem is actually to tar up what is in CVS. this is good in 
> > that i can
> > control which files in my dev tree are worth shipping. but it 
> > also means
> > it ships CVS dirs, and cvs is a pain to manage for manifests. but from
> > what i gather with your system, you build MANIFEST from the 
> > lib/ dir and
> > use the manifest.skip file to control it. i would like to have a
> > positive manifest file that i can edit (in addition or whatever). the
> > reason is that i have many temp and work in progress files in my dev
> > directory and i don't want to have to add each one to the skip
> > file. whereas i don't add new source files as frequently so editing a
> > manifest.in would be easier for me. this could take dirs and recurse
> > down them as well. so any answers or thoughts on a postive manifest.in
> > file?
> 
> Module::Build uses the same MANIFEST model as 
> ExtUtils::MakeMaker - it uses a MANIFEST file to determine what 
> should go in the distribution during 'Build dist' (and 'Build 
> disttest', etc.).  You can maintain this MANIFEST file by hand, 
> or it will auto-generate it if you do a 'Build manifest'.
> 
> So your hand-maintained MANIFEST should work just fine if I 
> understand your needs.
> 
> > i do appreciate your conceit that who needs make? one day when i have
> > mucho money to hire some good hackers, i will lead the creation of my
> > super make that will be DB backed, have bidirectional dependency
> > knowledge at all times, and have real knowledge about how to 
> > build stuff
> > instead of annoying templates and macros. i can dream. :)
> 
> Heh - I hope I didn't open a can of worms with this M::B 
> project, though sometimes it seems as if I did. ;-)

I AM YOUR FATHER, KEN.
JOIN THE DARK SIDE!

-- Darth Ingy

Re: [Module-build-general] Re: build and manifest

[Ken W. <ke...@ma...>]

On Tuesday, November 19, 2002, at 01:59  PM, Brian Ingerson wrote:

> On 19/11/02 10:59 +1100, Ken Williams wrote:
>> Heh - I hope I didn't open a can of worms with this M::B
>> project, though sometimes it seems as if I did. ;-)
>
> I AM YOUR FATHER, KEN.
> JOIN THE DARK SIDE!
>
> -- Darth Ingy

Funny, I just watched Episode 2 for the first time last night.

Better watch out - if our knowledge of The Code is insufficient 
to settle our dispute, we will have to use the rm -rf sabers.

  -Ken