Well, this is an interesting question that I have as a debian user: stable is still using postgresql 7.2. Current postgresql
version is up to 7.4, however. How can I keep my server running stable but also keeping a bit more up to date with versions of things?
Jen
In the case of PostgreSQL you can just compile it yourself as it has tools to enable you to upgrade your data stores built in.
Matt
I've been advised in the past that the trouble with compiling yourself in a debian system is that it breaks the integrity of the package system: do you mean here that you compile it and it kind of stays in sync with the apt system? Someone sent me a site offlist I didn't know existed: www.backports.org (thanks, Sue - tried to reply but it kept bouncing back).
Jen
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Fri, 2004-07-09 at 15:43, Jenny Hopkins wrote:
Well, this is an interesting question that I have as a debian user: stable is still using postgresql 7.2. Current postgresql
version is up to 7.4, however. How can I keep my server running stable but also keeping a bit more up to date with versions of things?
Jen
In the case of PostgreSQL you can just compile it yourself as it has tools to enable you to upgrade your data stores built in.
Matt
I've been advised in the past that the trouble with compiling yourself in a debian system is that it breaks the integrity of the package system: do you mean here that you compile it and it kind of stays in sync with the apt system? Someone sent me a site offlist I didn't know existed: www.backports.org (thanks, Sue - tried to reply but it kept bouncing back).
Jen
Yes, well... As with all Linux systems, you're either up-to-date or you break the package management system. AFAIK, the only exception to this rule is Gentoo.
Besides, for things like Apache, OpenSSL, Postfix, etc (things that are required to be configured securely) I always roll my own anyway and to hell with the package management system.
Matt
On 2004-07-09 21:36:06 +0100 Matt Parker matt@mpcontracting.co.uk wrote:
Yes, well... As with all Linux systems, you're either up-to-date or you break the package management system. AFAIK, the only exception to this rule is Gentoo.
I can't comment on them all, but this isn't true for most of the systems I use. You can build debs, rpms or other types of package for most systems. Of course, some distributions heavily patch some packages and don't provide good build tools or information, so it can be a lot of effort.
Besides, for things like Apache, OpenSSL, Postfix, etc (things that are required to be configured securely) I always roll my own anyway and to hell with the package management system.
Compile-time defaults should be secured in the distribution anyway and it's a bug if not IMO. The package system shouldn't interfere with your configurations (but some do).
On 2004-07-09 15:43:38 +0100 Jenny Hopkins Jenny@toby-churchill.com wrote:
In the case of PostgreSQL you can just compile it yourself as it has tools to enable you to upgrade your data stores built in.
I've been advised in the past that the trouble with compiling yourself in a debian system is that it breaks the integrity of the package system: do you mean here that you compile it and it kind of stays in sync with the apt system?
You can compile the latest debian packages on a stable system yourself. In the simplest case, you add a deb-src line for unstable to your sources.list, have installed things like debhelper and then run "apt-get source --build <packagename>".
Of course, things are hardly ever that simple and this is what the "backport" sources on www.apt-get.org spend most of their time dealing with. It can quickly become very complicated, so keep logbooks if you start trying to do this yourself. Do not build and test on a production machine if at all possible.