[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl-module-build
Subject:    Re: shipping multiple modules with Module::Build
From:       Ted Zlatanov <tzz () lifelogs ! com>
Date:       2008-07-09 20:29:56
Message-ID: 86prpm4x8b.fsf () lifelogs ! com
[Download RAW message or body]

On Wed, 9 Jul 2008 09:23:17 -0700 Eric Wilhelm <scratchcomputing@gmail.com> wrote: 

EW> # from David Golden
EW> # on Wednesday 09 July 2008 09:03:

>> In your Build.PL, the "module_name" just defines the main name that is
>> used to create the distribution file and so on.

EW> Yes.  But to be clear:  the 'module_name' gets used to name the dist.  
EW> It also is the default place to search for dist_author and 
EW> dist_version.

EW>   module_name => s/::/-/g => dist_name

Cool, thank you and David for all the help.

EW> Ted, I wouldn't call it bundling.  You're just shipping some extra .pm 
EW> files, they go in lib/ regardless of whether they are all in the same 
EW> namespace.

With EU::MM, this did not work for the tests, Lingua::BG::Numbers tests
could not load it, and I kept trying to find an explicit way to make it
work instead of trusting M::B.

EW> When your tarball hits PAUSE, the indexer will look at all of the .pm 
EW> files and add them to the index (provided that the name of a given 
EW> module has not been taken by another author.)  When a user says `cpan 
EW> LWP::Iterator::UserAgent`, they get the dotReader dist because the 
EW> index points their client to that tarball - and because I haven't 
EW> gotten around to tearing that module out as its own dist yet.

Great, thanks again for the help.

Ted
[prev in list] [next in list] [prev in thread] [next in thread]