Mailing List Archive: ModPerl: ModPerl

What happened with Apache2::Reload in mod_perl-2.0.4?

Index | Next | Previous | View Threaded

niels at perlboy

Apr 18, 2008, 1:14 AM

Post #1 of 8 (673 views)
Permalink

What happened with Apache2::Reload in mod_perl-2.0.4?

Hi mod_perl maintainers,

Thank you for releasing mod_perl 2.0.4.

I was wondering what happened to Apache2::Reload? Was it missed in
packaging for the upload to CPAN? If so then there may be other files
missing too.

Regards,
Niels

fred at redhotpenguin

Apr 18, 2008, 1:20 AM

Post #2 of 8 (652 views)
Permalink

Re: What happened with Apache2::Reload in mod_perl-2.0.4? [In reply to]

Niels van Dijke wrote:
> Hi mod_perl maintainers,
>
> Thank you for releasing mod_perl 2.0.4.
>
> I was wondering what happened to Apache2::Reload? Was it missed in
> packaging for the upload to CPAN? If so then there may be other files
> missing too.

See the Changelog:

Apache2::Reload has been moved to an externally maintained
CPAN distribution

http://search.cpan.org/dist/Apache-Reload-0.10/

>
> Regards,
> Niels
>

--
Red Hot Penguin Consulting LLC
http://www.redhotpenguin.com/

geoff at modperlcookbook

Apr 18, 2008, 5:03 AM

Post #3 of 8 (652 views)
Permalink

Re: What happened with Apache2::Reload in mod_perl-2.0.4? [In reply to]

Fred Moyer wrote:
> Niels van Dijke wrote:
>> Hi mod_perl maintainers,
>>
>> Thank you for releasing mod_perl 2.0.4.
>>
>> I was wondering what happened to Apache2::Reload? Was it missed in
>> packaging for the upload to CPAN? If so then there may be other files
>> missing too.
>
> See the Changelog:
>
> Apache2::Reload has been moved to an externally maintained
> CPAN distribution
>
> http://search.cpan.org/dist/Apache-Reload-0.10/

hmm...

I can't remember if I knew this or not, but we probably ought to treat
this like Apache-Test: keep bundling it with releases _and_ maintain
something separate on CPAN.

so I guess this means a mp2 release should (going forward) include _and_
imply a new release of

o mp2
o Apache-Test
o Apache-Reload

--Geoff

fred at redhotpenguin

Apr 18, 2008, 8:37 AM

Post #4 of 8 (650 views)
Permalink

Re: What happened with Apache2::Reload in mod_perl-2.0.4? [In reply to]

Geoffrey Young wrote:
>
>
> Fred Moyer wrote:
>> Niels van Dijke wrote:
>>> Hi mod_perl maintainers,
>>>
>>> Thank you for releasing mod_perl 2.0.4.
>>>
>>> I was wondering what happened to Apache2::Reload? Was it missed in
>>> packaging for the upload to CPAN? If so then there may be other files
>>> missing too.
>>
>> See the Changelog:
>>
>> Apache2::Reload has been moved to an externally maintained
>> CPAN distribution
>>
>> http://search.cpan.org/dist/Apache-Reload-0.10/
>
> hmm...
>
> I can't remember if I knew this or not, but we probably ought to treat
> this like Apache-Test: keep bundling it with releases _and_ maintain
> something separate on CPAN.

That's on the radar for 2.0.5, along with Apache::SizeLimit, to bundle
using svn:external. Phillip Gollucci brought this up about a month ago
or so, and I started to move on it but Gozer brought up a number of
things that had to be done to make this happen and the works with 5.10
release was pressing at that point.

Don't worry, I won't forget about it :)

>
> so I guess this means a mp2 release should (going forward) include _and_
> imply a new release of
>
> o mp2
> o Apache-Test
> o Apache-Reload
>
> --Geoff
>

--
Red Hot Penguin Consulting LLC
http://www.redhotpenguin.com/

pgollucci at p6m7g8

Apr 18, 2008, 1:05 PM

Post #5 of 8 (647 views)
Permalink

Re: What happened with Apache2::Reload in mod_perl-2.0.4? [In reply to]

Geoffrey Young wrote:
> so I guess this means a mp2 release should (going forward) include _and_
> imply a new release of
>
> o mp2
> o Apache-Test
> o Apache-Reload
> o Apache-SizeLimit

--
------------------------------------------------------------------------
Philip M. Gollucci (philip[at]ridecharge.com)
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

gozer at ectoplasm

Apr 21, 2008, 1:16 AM

Post #6 of 8 (615 views)
Permalink

Re: What happened with Apache2::Reload in mod_perl-2.0.4? [In reply to]

Fred Moyer wrote:
> Geoffrey Young wrote:
>>
>> Fred Moyer wrote:
>>> Niels van Dijke wrote:
>>>> Hi mod_perl maintainers,
>>>>
>>>> Thank you for releasing mod_perl 2.0.4.
>>>>
>>>> I was wondering what happened to Apache2::Reload? Was it missed in
>>>> packaging for the upload to CPAN? If so then there may be other files
>>>> missing too.
>>> See the Changelog:
>>>
>>> Apache2::Reload has been moved to an externally maintained
>>> CPAN distribution
>>>
>>> http://search.cpan.org/dist/Apache-Reload-0.10/
>> hmm...
>>
>> I can't remember if I knew this or not, but we probably ought to treat
>> this like Apache-Test: keep bundling it with releases _and_ maintain
>> something separate on CPAN.
>
> That's on the radar for 2.0.5, along with Apache::SizeLimit, to bundle
> using svn:external. Phillip Gollucci brought this up about a month ago
> or so, and I started to move on it but Gozer brought up a number of
> things that had to be done to make this happen and the works with 5.10
> release was pressing at that point.
>
> Don't worry, I won't forget about it :)
>
>> so I guess this means a mp2 release should (going forward) include _and_
>> imply a new release of
>>
>> o mp2
>> o Apache-Test
>> o Apache-Reload
o Apache-SizeLimit

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.

http://svn.apache.org/[...]/Apache-Test/tags/1.31

THat way, 2 things happen. First, we can always release mod_perl, without
having to worry about these external packages. We know what we are bundling
is exactly the same stuff that is _already_ on CPAN, great. Second, mod_perl
itself is protected from spurious failures caused by changes in any of these
modules before they are released.

The only negative is that if a change is made to say Apache-Test to fix a
problem mod_perl needs/wants, it complicates things a little. I make the
fix in A-T, making sure it fixes mod_perl's problem. If sure of that,
I proceed to release A-T. Once released, I can now test mod_perl against
this new A-T by locally changing the tag the svn:external is pointing to,
and if it solves to problem and doesn't create new ones, checkin the new
external definition.

I've dealt with 3rd packages in this way plenty, and it works.

Anyhting terribly obvious I am missing here ?

--
Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/ m/gozer\@(apache|cpan|ectoplasm)\.org/

Attachments:

signature.asc (0.24 KB)

pgollucci at p6m7g8

Apr 21, 2008, 3:17 PM

Post #7 of 8 (606 views)
Permalink

Re: What happened with Apache2::Reload in mod_perl-2.0.4? [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Philippe M. Chiasson wrote:
| 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.
|
| http://svn.apache.org/[...]/Apache-Test/tags/1.31
Lots of svn:externals at play here, all perl/modperl/tags/* should have
externals that point to other perl/[project]/tags/* otherwise the tags
are useless after the fact.

Ideally, we should _shutter_ branch for releases and update the
externals there so that the generated tar.gz contains the correct code
for us to vote on.

I believe I documented it this way for httpd/apreq

See also, Apache-DBI, Apache-Reload, and Apache-SizeLimits
I believe all 4 have RELEASE notes for this we can copy from.

| The only negative is that if a change is made to say Apache-Test to fix a
| problem mod_perl needs/wants, it complicates things a little. I make the
| fix in A-T, making sure it fixes mod_perl's problem. If sure of that,
| I proceed to release A-T. Once released, I can now test mod_perl against
| this new A-T by locally changing the tag the svn:external is pointing to,
| and if it solves to problem and doesn't create new ones, checkin the new
| external definition.
Something like that. Anyway you cut it, the other 3 have to be
'released' first if they have updates you need.

| Anyhting terribly obvious I am missing here ?
/me duck and hide

- --
- ------------------------------------------------------------------------
Philip M. Gollucci (philip[at]ridecharge.com)
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIDRJ2dbiP+9ubjBwRApkAAKCQfNKPWLX7gkl22Lk+DpUKXXi5twCeM5me
nKhZiYeES6UXYzSw0Z/IEaI=
=rppi
-----END PGP SIGNATURE-----

radek at pld-linux

Apr 23, 2008, 5:32 AM

Post #8 of 8 (596 views)
Permalink

Re: What happened with Apache2::Reload in mod_perl-2.0.4? [In reply to]

Philippe M. Chiasson <gozer[at]ectoplasm.org> [21-04-2008 09:16]:
> Fred Moyer wrote:
>> Geoffrey Young wrote:
[...]
>>> so I guess this means a mp2 release should (going forward) include _and_
>>> imply a new release of

>>> o mp2
>>> o Apache-Test
>>> o Apache-Reload
> o Apache-SizeLimit

> 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.

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
of everything.

[...]
> is exactly the same stuff that is _already_ on CPAN, great. Second, mod_perl
> itself is protected from spurious failures caused by changes in any of these
> modules before they are released.

...just this hypothetical situation?

> The only negative is that if a change is made to say Apache-Test to fix a
[...]

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ław Zieliński <radek[at]pld-linux.org>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com