Re: Can dist_version_from be evaluated at './Build dist' time?
# from Andreas J. Koenig # on Monday 23 June 2008 23:42: >dist_version_from => 'lib/.../Foo.pm' >(2) ./Build dist # builds the distro for 0.0.2 >(3) edit lib/.../Foo.pm > # development continues and Foo reaches 0.0.3 >(4) ./Build dist # again builds the distro for 0.0.2 > >I would have expected that step (4) builds the distro with 0.0.3 in >the name, instead it built 0.0.2 again. I had to re-run 'perl >Build.PL'. I believe that any info which could be a string or "..._from" in the constructor is going to display this behavior (e.g. abstract_from for META.yml) because of the way the build notes support works. It probably *should* pick-up on the change, but I think that means having more dependency targets (a lot of I/O churn on every action?) or adding checks in distmeta, etc. So, I don't think it is exactly intended, but that is how it is. --Eric -- So malloc calls a timeout and starts rummaging around the free chain, sorting things out, and merging adjacent small free blocks into larger blocks. This takes 3 1/2 days. --Joel Spolsky --- http://scratchcomputing.com ---
Re: Release META.yml 1.4
On Tue, Jun 24, 2008 at 1:33 AM, Jan Dubois <[EMAIL PROTECTED]> wrote: > I don't think it needs to be in 1.4, but it would be good to explicitly > declare the special status of the "perl" key in the requires section. > The synopsis of the spec indicates that you are supposed to be able to > specify a minimum Perl version this way, but actual spec section for > "requires" only allows Perl *modules* to be specified. +1 That's a great point. The Oslo Consensus (from the Oslo QA hackathon) agreed on supporting 'perl' as a special key for requires, configure_requires, etc. Having that enshrined in the META.yml spec would be a great way to ratify that sentiment. David
Re: Release META.yml 1.4
On Jun 24, 2008, at 03:42, David Golden wrote: That's a great point. The Oslo Consensus (from the Oslo QA hackathon) agreed on supporting 'perl' as a special key for requires, configure_requires, etc. Having that enshrined in the META.yml spec would be a great way to ratify that sentiment. Would that then be The Oslo Accords? :-P David
Re: Release META.yml 1.4
On Tue, Jun 24, 2008 at 11:55 AM, David E. Wheeler <[EMAIL PROTECTED]> wrote: > On Jun 24, 2008, at 03:42, David Golden wrote: > >> That's a great point. The Oslo Consensus (from the Oslo QA hackathon) >> agreed on supporting 'perl' as a special key for requires, >> configure_requires, etc. Having that enshrined in the META.yml spec >> would be a great way to ratify that sentiment. > > Would that then be The Oslo Accords? :-P One was a little easier to accomplish: * Consensus: http://use.perl.org/~Alias/journal/36128 * Accords: http://en.wikipedia.org/wiki/Oslo_accords :-)
Re: Release META.yml 1.4
On Tue, Jun 24, 2008 at 12:33 AM, Jan Dubois <[EMAIL PROTECTED]> wrote: > qI don't think it needs to be in 1.4, but it would be good to explicitly > declare the special status of the "perl" key in the requires section. > The synopsis of the spec indicates that you are supposed to be able to > specify a minimum Perl version this way, but actual spec section for > "requires" only allows Perl *modules* to be specified. Done. -Ken
Re: Release META.yml 1.4
On Mon, Jun 23, 2008 at 11:23 PM, David E. Wheeler <[EMAIL PROTECTED]> wrote: > On Jun 23, 2008, at 19:59, Ken Williams wrote: > >> Hearing none, I'll entertain a motion to copy >> http://module-build.sourceforge.net/META-spec-blead.html to >> http://module-build.sourceforge.net/META-spec-v1.4.html . > > +1 Done. Link for META-spec-current.html also adjusted accordingly. -Ken
