develooper Front page | perl.perl5.porters | Postings from January 2004

adding a new configure option to override the perl version during the dev cycle?

Thread Next
Stas Bekman
January 9, 2004 14:54
adding a new configure option to override the perl version during the dev cycle?
Message ID:
Every time RC1 is released I have to go a nuke all my pre-RC1 installs and 
reinstall from scratch, including CPAN modules. So for example now we had 
5.8.3-tobe which since 5.8.2 was released and until two days ago was called 
5.8.2, causing @INC to have all these /5.8.2/ and perl binary to be perl5.8.2. 
Besides annoying it's error-prone. I've updated 5.8.3 to RC1 but all my 
synlinks still pointed to the older perl which was linked to perl5.8.2 (which 
in fact wasn't 5.8.2 but 5.8.3-tobe). Finally many times I get confused when I 
test with 5.8.3 but see 5.8.2 in the path. This is counterproductive for me 
and probably for other people who need to smoke projects with maint/blead perl.

I've suggested to Nick to bump up a version number as soon as a new release is 
made. So for example when Nick releases 5.8.3, he could bump up the version 
number to 5.8.4 immediately. Nick explained that this suggestion is not very 
good, because some distros and users will install 5.8.4-tobe as 5.8.4 and then 
report bugs as if it was real 5.8.4. Which is not good and I agree with Nick.

So how about having a configure option for those of us who have to smoke perl 
and don't want to waste time rebuilding things when RC1 is released. So for 
example once Nick releases 5.8.3 I'd change my build scripts to use

   ./Configure ... -Dperl_version=5.8.4

(not sure about the name, suggestions?)

and once 5.8.4-RC1 is released, I'll just remove the above option. What do you 

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About