Short version- trying to use FPR to make an RPM and the --python-blahblahblah flags seem to not be working. I think they are being overwritten by something else and I'm hoping someone who understands package management better than I do (not hard) can suggest a culprit
Long version- I'm putting together some rpms to allow for installation of some custom python builds across a number of CentOS5 and 6 servers. I can't mess with the system python. I'm using FPM to make the RPMs out of tgz files downloaded directly from python.org and have set some flags to keep the installs confined to a specific folder (call it "/opt/abc/Python-[ver]" where ver is either 2.7 or 3.5)
BTW, I have some background in linux but not a lot so I apologize if I get any of the terminology wrong
mypascoconnect.
All of that is working but I noticed the bin file is ending up in the wrong place (in /opt/abc/ instead of in /opt/abc/Python-[ver]/) and a request was made to change the --python-package-name-prefix flag for FPM from the default of 'python' to a custom ex. 'ourpython'. To try and fix the bin issue I used the --python-install-bin flag on FPM.
neither of those FPM flags seemed change the install behavior at all, so far as I can tell. I suspect the effects are getting overwritten by one of the other flags set either in the fpm command or in the ./configure command but I just don't know package management well enough to say.
Here's the list of commands used:
Quote:
sudo fpm -s tar --prefix /opt/abc -t rpm -p ~/Python2.7.12.rpm --python-package-name-prefix ourpython --python-install-bin /opt/abc/Python-2.7.12/bin/ Python-2.7.12.tar
sudo yum install ~/Python2.7.12.rpm
sudo ./configure --prefix=/opt/abc
sudo make
sudo make altinstall
|
The bolded parts are the ones I think likely to be overriding the --python flags (italicized because why not?). Am I right about that?
