Front page | perl.perl5.porters |
Postings from April 2003
At 11:43 AM -0700 4/11/03, Brad Hughes wrote:
>PPrymmer@factset.com wrote:
>[...]
>>Do you want to retain the ability to run the source tree as your PERL_ROOT
>>or would it be OK to break that? Is this destined for 5.8.1 or later?
>
>Why break this?
The goal is to reduce breakage. We've had multiple instances in the
past of something not working as a result of failing to be completely
up-to-date in hundreds of lines of similar-looking code in
vms/descrip_mms.template. Even when this maintenance gets done it
diverts resources (i.e. my time) from the long list of other things
needing attention.
We might be able to create the temporary core directory and the
lib/pod directory in some other way than the way we do it now.
Possibly something as simple as the following two lines to replace
the hundreds of lines of individual dependencies we currently have:
BACKUP []*.h $(ARCHCORE)
BACKUP [.pod...] [.lib.pod...]
>I have many "installed" perls, choosable via on-the-fly
>redefinition, at process, job, or group levels, of PERL_ROOT.
I can't see that capability going away. I do the same thing and it's
not really related to whether the install target has been run.
>Actually, I've never understood the purpose of a separate "install" directory,
>especially with disk space so cheap.
Last time I checked, a cleaned-up build tree occupied about twice as
much space as an installed tree. Considering that we support
downright ancient systems, and especially considering how big Perl's
gotten, it's important, IMO, that the install target works properly.
I'm happy for it to remain optional if we can figure out a reasonable
way to do so.
--
________________________________________
Craig A. Berry
mailto:craigberry@mac.com
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
Thread Previous
|
Thread Next