-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Charles Wilson on 5/20/2008 10:23 PM:
|
| Counter-proposal: remove "--" handling in the wrapper, but don't worry
| about requiring "leading" options only. Instead, the wrapper just eats
| --${LTWRAPPER_OPTION_NAMESPACE}-* options (and their arguments) wherever
| they appear in the command line. However, allow the end-developer to
| set an environment variable (or a configure option?) to change what that
| prefix is.
Slightly better, but what about:
m4 --some-option --lt-...
You don't know whether --some-option takes an argument, and the developer
really intended to pass the literal string --lt-... as the argument to
that option, or if --some-option takes no argument, so --lt-... is a true
wrapper option. I'd really feel more comfortable if all --lt-* were
leading, since otherwise the wrapper can't distinguish options from option
arguments.
|
| That way, if package X insists on having options in the --lt-*
| namespace, package X's configure.ac could specify that, for this
| package, the magic wrapper namespace is --libtool-wrapper-* or whatever.
Having a configurable wrapper namespace sounds nice, but not mandatory.
|
| See above, and sorry for the trouble.
It's partly my fault, for suggesting it without realizing the ramifications
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgzpdgACgkQ84KuGfSFAYCNSACfaVFdJa5LaRiVAARt89+ccndg
g54AoK36w+1B8067ZAYecFWSJPruM9Sg
=NNQX
-----END PGP SIGNATURE-----
