Hi guys,

I'm now up and running on slackware 13 x64. I have noticed that the version of Python installed was 2.6.2 but there were a lot of bug fixes between this and 2.6.5. What is the best way to get 2.6.5 running on my machine. Do I have to install from source or is anybody aware of any packages that have been released?

Again, I'm not too familiar with package management systems on Slackware as I have always installed from source but this became a bit of a bind recently as updating software to newer versions involved a lot of hard work. Can anybody give me an ideas on the packaging systems available, the best ones to use, and where I can find information about the packages related to the package managers?

Lastly, (sorry long post), does anybody know if I can get Gedit working safely with XFCE?

Thanks well in advance!

Refer to "source/d/python/python.SlackBuild".

Why not?

Hi,

I think you could grab the Slackbuild from here...

http://slackware.osuosl.org/slackwar...urce/d/python/

Change all occurences of 2.6.4 to 2.6.5, get the Docs and source tarball from the web so as to match 2.6.5 version, remove all the patching in the Slackbuild, run it after chmoding it,

#chmod +x python.SlackBuild
#./python.SlackBuild

........

wadawadawadwada....


........



and you would get the installable package in /tmp.

Would bve enough to run

...#installpkg /tmp/Your-Python-2.6.5.txz

That's what I would do...

But do y think that Python 2.6.4 is still buggy...?

Nope, Python 2.6.4 would do the job so I'll settle for that one, just couldn't find a slackbuild for it.

I take it slackbuild is the way to go and more preferable to installing from source these days?

Yes. SlackBuilds create an easily installable/uninstallable package.

Thanks fellas, slackbuilding everything from now on....

I'd be very dubious about this as the patches contain changes for the lib64 directory structure from the lib standard as is present in Slackware64. They may well work with python 2.6.5 - the safest way would be to look at what they do and manually make the changes to the 2.6.5 source tree. Another way would be to look at the source and see if it's still compatible with the patches - they should however fail if the files don't match so you should be OK.
If it was me I'd just try running the Slackbuild with them in first and see what happens. Then if this fails start looking deeper.

The patches from 2.6.4 change the source files : sysconfig.py, Makefile.pre.in and readline.c. From what i can see they seem compatible with 2.6.5 source but I can't be certain so beware.

Obviously you'll have to change the versions in the Slackbuild.

The sources and Slackbuild for this version are in the -current tree here. This should "just work" (build) on SLackware64 13.

I recomend looking at the the Slackbook - I can't remember if this is on the install disk so forgive my ignorance.

Another very useful tool is Sbopkg from Chess Griffin. It is a tool to automate getting source and Slackbuilds from the Slackbuid site. As you may be noticing - Slackbuilds are a way of building Slackware packages from a script and are the very way all Slackware packages themselves are built.

Thanks bgeddy. Great tool.

There is also slapt-get and gsalpt. I know many Slackers don't like the dependency checking, but I've found for certain things (like the gnome-slackbuild-project, or parts thereof) slapt-get is quite nice.

These are not officially supported.