Hi all,
To be able to become portage a more general useable tool than just
within Gentoo Linux, it might be necessary to have it autotoolized
to say sth. like this:
# ./configure --prefix=/usr/local --with-managedroot=/my/packages --with-portageuser=haubi --with-portagegroup=tools BASH=/opt/bash/bin/bash PYTHON=/opt/sfw/python
# make
# make install
But to get these variables (BASH, PYTHON, etc.) into the py-files, one would think it is necessary to rename all the py-files to py.in, so that it would be hard to track changes while under CVS control.
I've found another mechanism to get variables substituted into the py-files and the bin-scripts. Using the script 'subst-install' does the substitution while installing the files, not at configure-time.
This is of course a first try of autotoolizing portage, and quite incomplete in the list of substituted variables (x86 only, no substitution for GPG yet, missing check for libc-version). And, well, it is against portage-2.0.51-r8.
Thus i have split the patch into three parts:
1) portage-autotoolize-A.patch:
add the files to become autotoolized.
This part should be more or less independant of portage-version,
and i've set the package version to "2.1" in configure.ac.2) portage-autotoolize-M.patch:
change existant files to recognize the configure-variables.
This is the hardest job: to find out where and how to use
substituted variables.3) portage-autotoolize-D.patch:
remove some junk-files (.orig), this is not essential.Hoping not to waste your time, Michael Haubenwallner -- Michael Haubenwallner SALOMON Automation GmbH Forschung & Entwicklung A-8114 Friesach bei Graz mailto:[EMAIL PROTECTED] http://www.salomon.at No HTML/MIME please, see http://expita.com/nomime.html
portage-autotoolize-A.patch.bz2
Description: application/bzip
Description: application/bzip
Description: application/bzip-- [email protected] mailing list
