Downgrading a version of Python in Slackware 13 64
 

Hi Forum

This may sound a bit of an awkward question, but I have this app, Salome-Platform, http://www.salome-platform.org/, It requires Python 2.5 at most to be able to run... ( compiling it is waaaay to complex.. )

Since the Python of Slackware is 2.6, can it be downgraded to 2.5...?

If it can, how do I do it...?

Thanks in Advance

Alex

if u have to downgrade, then you can use the python source from Slackware 12.2. just modify the slackbuild, using the current one as a sample.

Hi Slackd

You mean that if I build the Slack package, and then removepkg<current> and installpkg<downgraded> there will be no major incompatibilities...?

Cool... :-)

You realise that doing this in a Debian/*buntu would be simply suicidal... :-)

Everything is way too much entangled in those two Distros...

The closest thing to Slackware in terms of package independence is Red Hat/CentOS... right...?

Alex

dont use the remove pkg command...

use this command as often as u can while upgrading:

or just:

Good Luck~

The official release of slack64 came with python 2.6.2 so there is no downgrade. Compiling is not complex and now is a good time to start.

Download python 2.5 source and grab a slackware python build script for py 2.5.

Change the line
to
Run the build script and cross your fingers. Install py 2.5 and test your app. Post any problem you run into on this forum and I'm sure someone will be able to help with compiling.

A little extract from LFS:

Hope this is adequate :) :)

Sorry!! But i completely forgot about the Slamd64 project. You might wanna check here as this will be most appropriate for You. (x86_64)

as add-on to what others said, i would add suffix to python su it will not config with system stock python package. check configure options for that, it's usually --suffix=$SUFFIX_YOU_WANT_USE.

Debian/*buntu ( + Redhat EL, Fedora, CentOS etc.)
uses python for ' admin tools ' . Slackware doesn't
use python for anything, you could remove it, if
you wanted to do so.
.....

Hi Jedi_sith_fears,

I am not COMPILING Salome ( this is hardly compilable outside of the EDF development/Packaging environment... believing in the Salome Forum...)

Kind of "You know that you are a Linux Geek when you compile Salome-Platform under an arbitrary Distro..." :-)...

You get the point...

I am trying just to install it, but the installer script is Pyhon script...

But I will downgrade Py 2.6 and try it again...

Thankz everybody... :-)

Alex

Hi Forum...

:-(

I downgraded, but didnt do much... :

root@iskandhar:~/Desktop/InstallWizard_5.1.2_Debian_4.0_64bit# ls -la
total 572
drwxr-xr-x 7 root root 4096 2009-07-29 14:06 ./
drwxr-xr-x 6 root root 4096 2009-10-24 03:07 ../
drwxr-xr-x 4 root root 4096 2009-07-06 12:49 Products/
-rwxr-xr-x 1 root root 20815 2009-07-06 12:50 README*
-rwxr--r-- 1 root root 449541 2009-07-29 14:04 SALOME_5_1_2_Release_Notes.pdf*
drwxr-xr-x 3 root root 4096 2009-07-06 12:50 bin/
-rwxr-xr-x 1 root root 28140 2009-07-29 09:47 config_Debian_4.0_64bit.xml*
drwxr-xr-x 3 root root 4096 2009-07-06 12:50 config_files/
drwxr-xr-x 2 root root 4096 2009-07-06 12:50 doc/
-rwxr-xr-x 1 root root 52735 2009-07-06 12:50 runInstall*
drwxr-xr-x 2 root root 4096 2009-07-06 12:50 src/

root@iskandhar:~/Desktop/InstallWizard_5.1.2_Debian_4.0_64bit# ./runInstall
0 entries
root@iskandhar:~/Desktop/InstallWizard_5.1.2_Debian_4.0_64bit# python runInstall
root@iskandhar:~/Desktop/InstallWizard_5.1.2_Debian_4.0_64bit# sh: ./bin/SALOME_InstallWizard: No such file or directory
root@iskandhar:~/Desktop/InstallWizard_5.1.2_Debian_4.0_64bit# ls bin
SALOME_InstallWizard* lib/
root@iskandhar:~/Desktop/InstallWizard_5.1.2_Debian_4.0_64bit#


At moments like these i feel really stupid... :-(

Alex

Thx Jedi_sith_fears

I will try this, but I guess that there is a deeper problem... :-(

Thing is :

I have compiled brl-cad, and solved the MESA issue upgrading to <MESA current>, it works ok,
I creared a .bashrc file in ~ containing "export PATH=/usr/brlcad/bin:$PATH", as well as ". /usr/syrthes/syrthes-3.4.2/config-syrthes.sh" to source the environment of a thermal analysis program made by EDF called "Syrthes"...

Thing is that after logging as root, my .bashrc lives in /root, if I type mged ( which is the binary that lives in /usr/brlcad/bin ) and should call the CAD gui of BRL-CAD, it complains about unknown file or command... it does not "see" what i wrote in .bashrc, adding /usr/brlcad/bin to PATH,... but if i type "bash" it works then...

Trying to compile paraview with cmake yelds always the same stupid message that i must create a separate folder to build the binaries outsise paraview's directory...

but i DID this...

my paraview 3.6.1 folder lives in /root/Downloads/Paraview-3.6.1 and I #mkdir /root/home/build&&cd /root/home/build&&cmake /root/Downloads/Paraview-3.6.1/CMakeLists.txt...

It keeps saying that I should build in a folder separated of Paraview's source tree... which is what i am trying to do...


Seems that bash is not aware of the directory structure... but when I type pwd, it yelds the correct result...

I guess that all these things are somehow related... the install script of Salome not being able to find what it looks for, cmake not doing its job, bashrc not being initialized at login...


What do you think of this...?

What I am trying to do in Slackware works in Debian's/*buntu's/RHEL's/Fedora's/OPENSuse's

I guess i am just too n00b to use Slackware.... :-(

Somehow what used to work is not producing results...


BRGDS

Alex

/root/ is not supposed to be used for anything .. never !

Doing that ..and logging in as root is asking for trouble.
Always log in as 'username', use 'su' for admin tasks.
And building software : Only 'make install' should be done
as root. ( Use 'su' ).

The default build directory is /home/'user'/tmp/ ,
but you can have as many xxtmp as you wish.

.....

About cmake and build directory : A lot of applications,
also 'non cmake' requires an "outside" build directory.
.....