John Andersen wrote:
On Tuesday 05 December 2006 13:45, Adi Pircalabu wrote:
John Andersen wrote:
I have the opensuse repository for kde3 in my list of updates.
Today it has 77 updates, but in the process it wants to install spamassassin 3.1.3, which is back level by several releases. I run SA 3.1.7 and install from CPAN, and I don't want to go back to 3.1.3. Try http://repos.opensuse.org/home:/wrosenauer/[your_suse_ver]/, it has updated spamassassin rpm packages
Well Its not that I don't appreciate that, but historically suse has been extreemly late getting out updates to very time sensitive packages such as SpamAssassin. These packages are a month old.
Cpan at most 24 hours old.
1. What is important for you may not be that important for others 2. Newer does not always mean better/safer/faster. It rather means untested. For example: are you ready to offer tech support to companies for bleeding-edge software? Well, all you should do is remastering. from a technical standpoint. This usually is the most simple part. But is not enough. You, as an individual, are probably prepared to deal with newer versions of software (you are confortable to using CPAN). But how about your clients? Are you prepared to offer support on a contract basis using latest versions?
The real problem is a "recommended" package is treated like a dependency by the Software Updater.
A generic question: Why would it be so hard for a software updater package to check for the existance of packages installed by other means?
Why would you want this mix-up of package & source installed software? Especially, how can a vendor be able to offer support (a generic term for, let's say, software assurance) If a client requires a particular version of some software, so be it, you'll tailor the solution for them. But the stock version should always contain tested software. -- Adi Pircalabu -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org