NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
help them think they understand.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Drop a file in the distribution? (Score:1)
Really? A file? In each distro?
So I need 170 identical YAML files added to my repository, and then to change something I need to change 170 different config files?
Re: (Score:1)
... and all 170 yaml files need to contain my PAUSE admin login and password?
And in a repository that is visible to the public?
Re: (Score:1)
Actually, I skipped over some details in the post so as not to make everybody's eyes glaze over.
As it turn out to be, the configuration is first read from $ENV{HOME}/distrelease.yml (if it exists), which values can then be augmented/overrided from the local distrelease.yml. Although I have nowhere the gargantuan number of distros that you have, I'm not overly fond of needlessly replicating information either. :-)
Looks the same to me :) (Score:2)
You don't have to dig deep in Module::Release to do anything. You just make a method then call it. It's easy as pie. It's even easier in the 2.x stuff that's sitting on CPAN. If you haven't looked at it in awhile, take a peek even if to just steal ideas. When I get some time, I'll steal some of your ideas.
It's not a big deal if you write your own stuff. No one seems to use anything else that anyone writes anyway. :)
Your modules look a lot like the Module::Release stuff. I like that you configure it from a t
Re: (Score:1)
Instead of a full DSL, maybe you could do something like Module::Install does.
Make a really tight MI style set of commands that get you most of the way to a simple step by step process, such that we can fall back on pure perl and mix it together if needed.
Re: (Score:2)
Well, I think I have that. It's just that everything is a method call instead of a function call. Most of the release strict is either exposed scaffolding (which I really would like to fix when I have enough free time to fix things that work), or just a declaration of steps.
But, that's something to think about later. If someone really wanted it I might change it, but since the three people in this thread all have their own release software that no-one else uses, I'm not very motivated. :)
Re: (Score:1)
Your modules look a lot like the Module::Release stuff.
What can I say? I may be foolish enough to reinvent the wheel, but yet I know better than not let myself be inspired by what's already there. :-)
You don't have to dig deep in Module::Release to do anything. You just make a method then call it. It's easy as pie.
I'll give you that it's not that deep, and that it's not too hard, but I kinda balk at having to hack into the 'release' script if I want to add a new 'check_somethingelse()' action, or