Re: What happened with Apache2::Reload in mod_perl-2.0.4?
Content-Type: text/plain; charset=utf-8
Philippe M. Chiasson <firstname.lastname@example.org> [21-04-2008 09:16]:[color=blue]
> Fred Moyer wrote:[color=green]
>> Geoffrey Young wrote:[/color][/color]
>>> so I guess this means a mp2 release should (going forward) include _and=[/color][/color][/color]
>>> imply a new release of[/color][/color][/color]
>>> o mp2
>>> o Apache-Test
>>> o Apache-Reload[/color][/color]
> o Apache-SizeLimit[/color]
> And as the latest Release Manager, I must say that having to release 3
> extra CPAN modules along with each mp2 releases is going to be a PITA.[/color]
Then why bother with that, and not just keep them separate?
Separate is nice. Smaller packages, smaller repository, possibly
different people commiting, one bug doesn't require release / rebuild
> is exactly the same stuff that is _already_ on CPAN, great. Second, mod_p=[/color]
> itself is protected from spurious failures caused by changes in any of th=[/color]
> modules before they are released.[/color]
=2E..just this hypothetical situation?
> The only negative is that if a change is made to say Apache-Test to fix a[/color]
BTW, currently the Apache::Test version in 2.0.4 is 1.31, while the
latest one on CPAN is 1.30.
This is a bit of a PITA while packaging. I want to package both mp2
and the latest Apache::Test; preferably separately (vserver users
whine a lot when having to install something they don't need). So,
both apache-mod_perl and perl-Apache-Test packages. Now, I could switch
between the CPAN version and bundled version of Apache::Test (depending
on which one is later at the moment), but it's heavily annoying...
Rados=C5=82aw Zieli=C5=84ski <email@example.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
-----END PGP SIGNATURE-----