On Wed, Mar 15, 2000 at 03:16:16AM -0300, Alexandre Oliva wrote:
> On Mar 13, 2000, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
>
> > I would still like to see {auto{conf,make},libtool} use Ralf
> > Engelschall's shtool (or a variant of it) to encapsulate the
> > portability issues of things like mkdir -p and mkdir -m 700 into a
> > single script rather than scattered across the sources...
>
> Yup. Something like this has been suggested for automake's
> `missing', and I'm thinking about the best way to make it work.
That was me! =)O| Actually Tom said several people recommended that
approach to him independently.
> I've just tought we could keep it in an initial section of
> `configure'. Then, we'd arrange for `autoconf' to preserve that
> section, and we'd need some tool to add/remove/update shtools within
> that special section of configure. Comments?
The shtool distribution comes with code to combine tools into a single
script, so we could probably use that as a basis.
I was wondering when in the package lifecycle the appropriate scripts
should be chosen and tacked into configure? Might autoconf perhaps
start to ship a comprehensive set which it installs into the package
source tree at autoconf time, and then running configure could tack
only the shtool's needed on the build host on to the front of
config.status? I'll bet Akim would love to write a macro to do all
this =)O| =)O|
That might be overkill (I guess it depeds on how many shtool's we are
likely to end up with), and perhaps tacking them all onto the front of
configure at autoconf time would be plenty good enough for half a
dozen or so.
Either way, adding them to the front of an existing script is
priceless. There are already too many shell droppings in
autoconfiscated packages!
Cheers,
Gary.
--
___ _ ___ __ _ mailto:[EMAIL PROTECTED]
/ __|__ _ _ ___ _| | / / | / /_ _ _ _ __ _| |_ __ _ ___ [EMAIL PROTECTED]
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
\___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page: /___/ /___/ gpg public key:
http://www.oranda.demon.co.uk http://www.oranda.demon.co.uk/key.asc
