Porting Orphans : (was: apache::sandwich)

[si...@siberian.org]

This brings up a good point, is there a list of 'ModPerl 
Orphans' anywhere? For the most part I would imagine that 
a modules author/maintainer will manage the transition to 
mp2 but there must be a ton of modules that are Orphans 
with little hope of making it over unless some kind 
developer makes it happen.

It would be pretty great if there was a list and people 
could start taking responsibility for the tasks to avoid 
duplicate work as well as to guide folks who have time to 
contribute and are not sure where to start.

Lame suggestion most likely. I was just thinking 'I would 
like to try to port something but where to start....'

If there is interest in this I can put up a page for this 
sort of thing and send email out to all of the existing 
authors, hunting for orphans to post.

John-

On Mon, 10 Mar 2003 12:31:05 -0800 (PST)
  Nick Tonkin <ni...@tonkinresolutions.com> wrote:
>Another option would be for you to port Apache::Filter to 
>run under mp2.
>Then your code as well as anyone else's who uses that 
>module would run
>unchanged under mp2. That would be a Good Thing and you'd 
>be a mod_perl
>hero. People on this list would help if you got stuck, 
>and the
>documentation for porting is getting quite extensive.
>
>This doc: 
>http://perl.apache.org/docs/2.0/devel/porting/porting.html 
>is
>what you want.
>
>Good luck,
>
>- nick
>
>-- 
>
>~~~~~~~~~~~~~~~~~~~~
>Nick Tonkin   {|8^)>
>

Re: Porting Orphans : (was: apache::sandwich)

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

siberian@siberian.org wrote:
> This brings up a good point, is there a list of 'ModPerl Orphans' 
> anywhere? For the most part I would imagine that a modules 
> author/maintainer will manage the transition to mp2 but there must be a 
> ton of modules that are Orphans with little hope of making it over 
> unless some kind developer makes it happen.
> 
> It would be pretty great if there was a list and people could start 
> taking responsibility for the tasks to avoid duplicate work as well as 
> to guide folks who have time to contribute and are not sure where to start.
> 
> Lame suggestion most likely. I was just thinking 'I would like to try to 
> port something but where to start....'
> 
> If there is interest in this I can put up a page for this sort of thing 
> and send email out to all of the existing authors, hunting for orphans 
> to post.

It's a good idea to compile a list of modules that need to get ported, 
discarding those that aren't needed in mp2 (e.g. Apache::Filter and 
FilterChain are definitely to stay in the mp1 world I believe). However there 
is a problem with porting modules that include XS code, since the replacement 
for Apache::src hasn't been completed yet. Pure perl modules porting should be 
fine.

FWIW, I've ported Apache::Peek and Apache::Scoreboard to 2.0, but I can't 
release them yet as they need a support from mod_perl-2.0 (because of 
Apache::src/xs stuff), which wasn't committed yet. We are hoping to deliver a 
much better Makefile.PL support (including things like installing into 
Apache2/ and automatic configuration of the MM attributes for compilation)

__________________________________________________________________
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