bergman on 24 Aug 2012 09:16:45 -0700


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[PLUG] CentOS stability vs newer packages (Was: no longer anything at all to do with Re: Tried of Windows...)


In the message dated: Fri, 24 Aug 2012 10:37:44 EDT,
The pithy ruminations from Sam Gleske on 
<Re: [PLUG] Tried of Windows...> were:
=> On Fri, Aug 24, 2012 at 9:27 AM, Rich Freeman <r-plug@thefreemanclan.net> wrote:
=> > On Thu, Aug 23, 2012 at 3:59 PM, JP Vossen <jp@jpsdomain.org> wrote:
=> >> If you can stay only with stuff in the stock repos you are OK to get it
=> >> installed, but even then a lot of that is just too old.
=> >>

I run CentOS on the machines at $WORK. I'm retiring our CentOS4 boxes as soon
as possible (support ends this year), and beginning to move from CentOS5 to
CentOS6.

Some of the developers here would like to see newer versions of a lot of
packages, but when the business and infrastructure depend on the servers, I
will almost always choose stability over the 'newest' version.

Having said that, there are some good ways to deal with the inevitable tension
between a stable "enterprise" distribution and having newer packages:

	The EPEL repository provides newer packages from the Fedora line,
	built and packaged for Centos.
		http://fedoraproject.org/wiki/EPEL/FAQ

	The CentOSPlus packages are similar updates, less 'bleeding edge'
	than EPEL, but a much smaller range:
		http://wiki.centos.org/AdditionalResources/Repositories/CentOSPlus

	The "alternatives" package can ease the process of seamlessly making
	newer versions of a package available without disrupting PATHs, etc.
		man alternatives

	The "environment-modules" package is a terrific way to allow users
	to select from multiple installed versions of products. This
	doesn't address any issues of building packages or OS-level
	compatibility (ie.,  release 4 of 'foobar' requires a newer
	glibc than CentOS5 provides), but it does make it easy to set up
	a consistent environment using different versions. For example,
	we've got 3 different versions of python installed, and packages
	(local & external) that use python. Users here can select their
	peferred python version, and configuration files using the
	"environment-modules" package ensure that they'll get the right
	version of dependent programs.

	Example:

		which python
		/lab/software/python/2.5/bin/python
		which foobar
		/lab/software/foobar/1.2/bin/foobar

		module load python/2.7
		/lab/software/python/2.7.2/bin/python
		which foobar
		/lab/software/foobar/1.4a/bin/foobar

	See:
		man module
	
Mark
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug