Downgrading a version of Python in Slackware 13 64

Alexvader · 10-26-2009, 11:03 AM

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

slackd · 10-26-2009, 11:39 AM

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.

Alexvader · 10-26-2009, 11:48 AM

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

slackd · 10-26-2009, 11:52 AM

dont use the remove pkg command...

use this command as often as u can while upgrading:

Code:

upgradepkg --reinstall --install-new *t?z

or just:

Code:

upgradepkg --install-new *t?z

Good Luck~

tux_dude · 10-26-2009, 11:56 AM

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

Code:

ARCH=${ARCH:-i486}

to

Code:

ARCH=${ARCH:-x86_64}

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.

slackd · 10-26-2009, 12:01 PM

Quote:

Originally Posted by Alexvader

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

Alex

A little extract from LFS:

Quote:

Creating Package Archives

In this scheme, the package installation is faked into a separate tree as described in the Symlink style package
management. After the installation, a package archive is created using the installed files. This archive is then used to
install the package either on the local machine or can even be used to install the package on other machines.
This approach is used by most of the package managers found in the commercial distributions. Examples of
package managers that follow this approach are RPM (which, incidentally, is required by the Linux Standard Base
Specification), pkg-utils, Debian's apt, and Gentoo's Portage system. A hint describing how to adopt this style of
package management for LFS systems is located at http://www.linuxfromscratch.org/hint...files/fakeroot.
txt.
Creation of package files that include dependency information is complex and is beyond the scope of LFS.
Slackware uses a tar based system for package archives. This system purposely does not handle package dependencies
as more complex package managers do. For details of Slackware package management, see http://www.slackbook.org/html/package-management.html

Hope this is adequate

slackd · 10-26-2009, 12:27 PM

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

ozanbaba · 10-26-2009, 01:47 PM

Quote:

Originally Posted by Alexvader

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

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.

knudfl · 10-26-2009, 01:49 PM

Quote:

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

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.
.....

jedi_sith_fears · 10-26-2009, 02:40 PM

As far as I got from Salome website,

Quote:

Third-party dependencies

The SALOME platform relies on a set of third-party softwares. The current version depends on the following list (versions given here are from Debian Sarge, except OpenCascade, VTK and MED, which are not Debian packages):

CAS-5.2.4 OpenCascade (try binaries,a source patch is needed)
VTK-4.2.6 VTK 3D-viewer
PyQt-3.13 Python-Qt Wrapper
Python-2.3.5 Python interpreter
SWIG-1.3.24 SWIG library
boost-1_32_0 C++ library (only include templates are used)
hdf5-1.6.2 Files Database library
med-2.2.2 MED Data Format support for file records
omniORB-4.0.5 ORB used in SALOME
qt-x11-free-3.3.3 Qt library
qwt-4.2 Graph components for Qt
sip4-4.1.1 langage binding software

And, in order to build the documentation:

doxygen-1.4.2
graphviz-2.2.1

Additionnal software may be installed for optional features:

netgen4.3 + patch
tix8.1.4
openpbs-2.3.16
lsf-???

The salome 5.1.2 Documentation pdf also describes compatibility with python 2.6 is provided. Which version of salome are you compiling?

Quote:

Summary: compatibility python 2.6 in import_hook
Change:
Compatibility with Python 2.6 has been provided

Alexvader · 10-26-2009, 06:56 PM

Quote:

Originally Posted by jedi_sith_fears

As far as I got from Salome website,

The salome 5.1.2 Documentation pdf also describes compatibility with python 2.6 is provided. Which version of salome are you compiling?

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

Alexvader · 10-26-2009, 07:15 PM

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

jedi_sith_fears · 10-26-2009, 11:30 PM

Try the debian etch or mandriva 2008 version, see if thatt works

Alexvader · 10-27-2009, 10:34 AM

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

knudfl · 10-28-2009, 03:32 AM

Quote:

/root/Downloads/Paraview-3.6.1

/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.
.....