On 10/26/11 08:21, Danek Duvall wrote:
Rich Burridge wrote:
http://jurassic.us.oracle.com/~richb/6835038-v1
If I understand this correctly, when it's looking for a python interpreter,
it'll check in the order in the list. Should that order be in the
"system-approved" order? That is, because 2.6 is the default, try that
first? In particular, I'd be apprehensive about any other userland
components which might use this picking up something that's not the default
and end up using that by accident.
Shouldn't the unversioned python be the system preferred version?
Also remember that these files are used when generating configure scripts and
most userland/jds/X components will build with the ones that the upstream
project generated and included in the tarballs. Only those that run
autoreconf as part of their build (because they patched configure.ac or
Makefile.am or similar) would see the versions from the Solaris provided *.m4
files.
Being different from upstream would also mean that those of us who generate
tarball releases for upstream components, or build from raw git/hg/svn repos
from upstream during development, are producing different results when
doing that on Solaris vs. Linux, and while some amount of difference comes in
just because we all have different autoconf/automake versions, changing the
python search order seems likely to cause more problems there than it solves.
--
-Alan Coopersmith- [email protected]
Oracle Solaris Platform Engineering: X Window System
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
