On Thu, 30 Aug 2001, Doug MacEachern wrote:
> On Thu, 30 Aug 2001, Stas Bekman wrote:
>
> > Doug, we do scan for core files but we don't ensure that the environment
> > is supportive for the creation of the core files in first place. So not
> > having core files found by scanning, doesn't mean that everything is
> > dandy.
> >
> > Should we use BSD::Resource or 'ulimit -c unlimited' before starting
> > 'make test'? and then restoring the value at the end? It's much better
> > when the test environment worries to do that for us and future users, than
> > just adding a note somewhere.
>
> that would be great stas. provided BSD::Resource is optional of course :)
> any interest on writing the bundle.tar.gz generator? would be really
> handy to start adding new modules such as this and updating (lwp and
> friends are getting outdated in the current bundle), without having todo
> it by hand.
I've already started working on it a few days ago, but I'm very sick all
this week, so I haven't much done yet :(
One of the problems I'm think about is once I've all the packages in
place, how do I know the order of their build/install, to satisfy
prerequisites, even if all the required sources are near. I guess I need
to steal this code from CPAN.pm.
But assuming that the user is on Unix-flavored system, there is always
'sh', so 'ulimit' can be used. Not sure though how can we set it
automatically in the parent shell before running ./t/TEST. How about
Makefile?
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://localhost/ http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
