Re: YAML and Makefile.PL (was various topics)

In article <[EMAIL PROTECTED]>, Adam Kennedy <[EMAIL PROTECTED]> wrote: > The big advantage I see here is it's not you doing the work, it's > everybody else. > > I generally don't have too much of a problem doing incrementals... > > cd trunk/Module-Name > ppichangeversion 0.14 0.15 > perl ../..

Re: YAML and Makefile.PL (was various topics)

Moin, On Tuesday 31 January 2006 06:50, chromatic wrote: > On Monday 30 January 2006 20:40, Adam Kennedy wrote: > > Incremental releasing is a toolchain problem. [snip a good comparisation] > I don't say this often, but that really doesn't seem scalable to me. > If I have to re-release a distrib

Re: YAML and Makefile.PL (was various topics)

On Jan 31, 2006, at 2:32 AM, Adam Kennedy wrote: But then how are you going to make Bundle::CPAN trigger when there's a critical failure, without requiring the user to be smart? CPAN.pm and CPANPLUS.pm already check their own version against CPAN on every run. All we'd need to do is have A

Re: YAML and Makefile.PL (was various topics)

On Jan 31, 2006, at 2:30 AM, Adam Kennedy wrote: Solutions that can be implement without either betting incredibly aggressive to users, putting MB or CPANPLUS into the core, or going down the bundled route, would be interesting to hear though. If I've read the perl5-porter summaries correct

Re: YAML and Makefile.PL (was various topics)

A. Pagaltzis wrote: * chromatic <[EMAIL PROTECTED]> [2006-01-31 08:20]: Perhaps CPAN/CPANPLUS should check for updates? Maybe just add EUMM+MB to Bundle::CPAN? (Does CPANPLUS have an equivalent?) Regards, But then how are you going to make Bundle::CPAN trigger when there's a critical failu

Re: YAML and Makefile.PL (was various topics)

A. Pagaltzis wrote: * Adam Kennedy <[EMAIL PROTECTED]> [2006-01-31 07:50]: There isn't really any very good way (that I can see at least) to ensure that an end-user gets an update to EUMM/MB, just the module packager. So maybe that is the fundamental problem that should be addressed? Regards,

Re: YAML and Makefile.PL (was various topics)

* chromatic <[EMAIL PROTECTED]> [2006-01-31 08:20]: >Perhaps CPAN/CPANPLUS should check for updates? Maybe just add EUMM+MB to Bundle::CPAN? (Does CPANPLUS have an equivalent?) Regards, -- Aristotle Pagaltzis //

Re: YAML and Makefile.PL (was various topics)

* Adam Kennedy <[EMAIL PROTECTED]> [2006-01-31 07:50]: >There isn't really any very good way (that I can see at least) >to ensure that an end-user gets an update to EUMM/MB, just the >module packager. So maybe that is the fundamental problem that should be addressed? Regards, -- Aristotle Pagalt

Re: YAML and Makefile.PL (was various topics)

On Monday 30 January 2006 23:15, A. Pagaltzis wrote: > * Adam Kennedy <[EMAIL PROTECTED]> [2006-01-31 07:50]: > >There isn't really any very good way (that I can see at least) > >to ensure that an end-user gets an update to EUMM/MB, just the > >module packager. > So maybe that is the fundamental

Re: YAML and Makefile.PL (was various topics)

chromatic wrote: On Monday 30 January 2006 20:40, Adam Kennedy wrote: Incremental releasing is a toolchain problem. Having to rerelease more than one module and making every one of my users upgrade every module that uses this tool -- not just my one or more modules -- rather than making eve

Re: YAML and Makefile.PL (was various topics)

chromatic wrote: On Monday 30 January 2006 20:40, Adam Kennedy wrote: Incremental releasing is a toolchain problem. Having to rerelease more than one module and making every one of my users upgrade every module that uses this tool -- not just my one or more modules -- rather than making e

Re: YAML and Makefile.PL (was various topics)

On Monday 30 January 2006 20:40, Adam Kennedy wrote: > Incremental releasing is a toolchain problem. Having to rerelease more than one module and making every one of my users upgrade every module that uses this tool -- not just my one or more modules -- rather than making every one who uses the

Re: YAML and Makefile.PL (was various topics)

brian d foy wrote: In article <[EMAIL PROTECTED]>, Adam Kennedy <[EMAIL PROTECTED]> wrote: And if there is a problem with Module::Install, you have to update all your dists with the new version - solve one problem, create two new ones :) But if there is a problem with EU::MM or Module::Build

Re: YAML and Makefile.PL (was various topics)

In article <[EMAIL PROTECTED]>, Adam Kennedy <[EMAIL PROTECTED]> wrote: > > And if there is a problem with Module::Install, you have to update all > > your dists with the new version - solve one problem, create two new > > ones :) > But if there is a problem with EU::MM or Module::Build, you ha

Re: YAML and Makefile.PL (was various topics)

Except for the little fact that you have to bundle Module::Install in all of your modules and need not to forget to add inc/* to MANIFEST - Graph::Easy::As_svg increases from 27K to 47K gzipped That concerned me for a little while as well. But then someone pointed out to me that disk space

Re: YAML and Makefile.PL (was various topics)

Tels did write: Moin, [...] So, MakeMaker should be fixed to generate proper META.ymls without the kludges nec that I needed. Of course, Schwern wills say "patches welcome" and I am not up to patch MakeMaker :-( (The other way would be the META.yml file for CPAN to be generated, but that

Re: YAML and Makefile.PL (was various topics)

On Sunday 29 January 2006 12:51, Tels wrote: > Moin, > > On Sunday 29 January 2006 12:27, Adam Kennedy wrote: > > As I mentioned early, the obvious upgrade path from EU:MM, > > (apparently if you don't care about 5.004 at least) is to > > Module::Install. > > > > For example... > > > > As far as I

Re: YAML and Makefile.PL (was various topics)

Moin, On Sunday 29 January 2006 12:27, Adam Kennedy wrote: > As I mentioned early, the obvious upgrade path from EU:MM, (apparently > if you don't care about 5.004 at least) is to Module::Install. > > For example... > As far as I can tell, it does what you want. Except for the little fact that y

Re: YAML and Makefile.PL (was various topics)

As I mentioned early, the obvious upgrade path from EU:MM, (apparently if you don't care about 5.004 at least) is to Module::Install. For example... Makefile.PL --- use inc::Module::Install; name 'File-ShareDir'; all_from 'lib/File/Share

Re: YAML and Makefile.PL (was various topics)

On Sun, Jan 29, 2006 at 12:04:22PM +0100, Tels wrote: > Just witness Graph::Dependency, it will fail when their is no META.yml > available, and what do you want me to do then? Parse Makefile.PLs? The "correct" WTDI is to execute the Makefile.PL and parse the resulting Makefile, looking for the PR

YAML and Makefile.PL (was various topics)

Moin, On Sunday 29 January 2006 06:37, you wrote: > Tels, > > Please forgive me for being blunt, but I think it's your fault for > writing fragile META.yml creation code. You are right for the code being fragile. (and no offense taken :) But there was no other way I could get the license field