Perl-10: solaris; how to run configure with NO asks, but NOT /usr/local?

Answering all these freaking questions -- you start getting used to
hitting for each one, then OOPS, I didn't mean that (that
G.D. "/usr/local"! -- which I *never* want), and now what do I do?

Well, just keep going, and later on edit the makefile, I suppose.

No, I want to start over, but this time specify up front that
I want everything installed right there under the same directory
I untarred the .gz into.

(I'll get to the executables, etc, via symlinks. And I
assume that if I run the correct executable, it'll know
where to look for its own version's libraries are (that
of course came out of the .tar.gz-file.))

Make any sense?

Basically I want to keep these various perl's totally separate.

Maybe there's a better way. You tell me.


Oh, why no /usr/local. Because the way I partitioned the
disk at the os-install a few years ago, there now not enough
room. And even if there were, I'd still have the separate
perl versions colliding.


Question: how do YOU build a perl? You don't actually sit there
answering each of a gillion (sp?) questions, do you?



Thanks!

David

Re: Perl-10: solaris; how to run configure with NO asks, but NOT /usr/local?

Quoth dkcombs@panix.com (David Combs):
> Answering all these freaking questions -- you start getting used to
> hitting for each one, then OOPS, I didn't mean that (that
> G.D. "/usr/local"! -- which I *never* want), and now what do I do?

Read INSTALL?

> Well, just keep going, and later on edit the makefile, I suppose.

Configure gives you the option to edit config.sh (which is what you
should be doing if you got something wrong) at the end. Also, at any
question you can answer &-d to take the default answer to all subsequent
questions.

> No, I want to start over, but this time specify up front that
> I want everything installed right there under the same directory
> I untarred the .gz into.

That's a really bad idea. Create another directory parallel to the one
you untarred into; that is, if you untarred into
/home/me/perl/perl-5.8.8 then install in
/home/me/perl/perl-5.8.8-installed or something similar.

> (I'll get to the executables, etc, via symlinks. And I
> assume that if I run the correct executable, it'll know
> where to look for its own version's libraries are (that
> of course came out of the .tar.gz-file.))

The path to the configured install directory is hard-coded, so yes,
assuming you can locate the executable it can handle locating its own
libraries.

> Question: how do YOU build a perl? You don't actually sit there
> answering each of a gillion (sp?) questions, do you?

../Configure -des \
-Uinstallusrbinperl -Dusedevel -Uversiononly \
-Dman1dir=none -Dman3dir=none \
-Dhtml1dir=none -Dhtml3dir=none \
-Dprefix=$inst \
$confargs

where $inst is where I want it installed, and $confargs is anything like
-Duseithreads or -Duse64bitint I want this perl built with. The
-Dusedevel -Uversiononly options are only useful if you are installing a
development version of perl.

Ben