[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
==================*/