Alan Coopersmith wrote: > Shouldn't the unversioned python be the system preferred version?
No. /usr/bin/python will be a mediated link, which the user can retarget to whatever version they choose. (Pkglint needs mediated link support, which is why it's not done yet.) I suppose we could add a symlink somewhere that always pointed to the system default, but I don't think that ends up being a panacea, either. > 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. Fair enough. > 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. Okay. We should just make sure that any components that use python be very careful to choose the correct version. Danek _______________________________________________ userland-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/userland-discuss
