From: Joseph Marton (jmmarton_at_gmail.com)
Date: Tue Aug 07 2007 - 14:50:27 CEST
Message-ID: <859ece290708070550u667b3afdm2c57e059cc5479e9@mail.gmail.com> Date: Tue, 7 Aug 2007 07:50:27 -0500 From: "Joseph Marton" <jmmarton@gmail.com> Subject: Re: [suse-sles-e] Re: SLES9 and MySQL5
That's both good and bad, though. If I go and view info on a product,
say MySQL, I can easily see what's new/fixed in a specific version of
the product. But with the backporting in SLES, it's more difficult to
determine if the features or fixes I'm looking for are included. So
in this situation, the higher version number is basically an indicator
to let me know if the product has what I need.
I'm not sure how you overcome this exactly, but it would definitely be
nice to see something put into place so that people know that version
X of a product in SLES is equivalent to version X of the product if
downloaded directly from that product's source.
Joe
On 8/7/07, Rasmus Plewe <rplewe@suse.de> wrote:
> Because of our backporting policy, often requests for a new version
> really are just request for a higher version number, because relevant
> features have been backported. There is a widespread "newer is better"
> belief, which is not always justified...
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Aug 07 2007 - 16:54:14 CEST