eliminating modperl-2.0/patches dir?

[Stas Bekman <st...@stason.org>]

You discover interesting things when doing release packaging.

Apparently we had an apache patch to do static modperl for years at: 
modperl-2.0/patches/link-hack.pat
I suppose it's no longer needed, right Philippe?

There is also modperl-2.0/patches/c-scan.pat which is the patch against 
the original C::Scan to make it working with our source scanner, but it's 
long outdated and we now have ModPerl::CScan that has all the needed 
fixes. So I suppose we can nuke that patch as well.

If this directory becomes empty, should we keep it at all, in case we will 
want to store some patches there? or should we just get rid of it?

-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org

Re: eliminating modperl-2.0/patches dir?

["Philippe M. Chiasson" <go...@ectoplasm.org>]

Stas Bekman wrote:
> You discover interesting things when doing release packaging.
> 
> Apparently we had an apache patch to do static modperl for years at: 
> modperl-2.0/patches/link-hack.pat
> I suppose it's no longer needed, right Philippe?

My godness, we sure don't need that thing around anymore, as it's patching
httpd-core among other things. It looks like a proof-of concept, like the
one I re-created when initially trying to get the static build out.

+1 to throw it out

> There is also modperl-2.0/patches/c-scan.pat which is the patch against 
> the original C::Scan to make it working with our source scanner, but it's 
> long outdated and we now have ModPerl::CScan that has all the needed 
> fixes. So I suppose we can nuke that patch as well.

+1 (Any reasons why we couldn't get our C::Scan patches back into C::Scan ?)

> If this directory becomes empty, should we keep it at all, in case we will 
> want to store some patches there? or should we just get rid of it?

Well, you can't _really_ get rid of it with CVS, can't you? Once empty, it will
just vanish until someone adds something to it once more.

-- 
--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/     F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5