From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2013-January/021887.html | 159 ++++++++++++++++++++++++++++ 1 file changed, 159 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/021887.html (limited to 'zarb-ml/mageia-dev/2013-January/021887.html') diff --git a/zarb-ml/mageia-dev/2013-January/021887.html b/zarb-ml/mageia-dev/2013-January/021887.html new file mode 100644 index 000000000..9eb23709f --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/021887.html @@ -0,0 +1,159 @@ + + + + [Mageia-dev] What's the point of the latest nvidia update? + + + + + + + + + +

[Mageia-dev] What's the point of the latest nvidia update?

+ Robert Wood + robert.wood at apostrophe.co.uk +
+ Sun Jan 20 22:16:34 CET 2013 +

+
+ +
So you're saying that because v295 has been out a while you feel it's 
+stable so you're happy to have that in the official repositories? I can 
+kind of understand that, although in the case of nvidia you'd think they 
+had already done the bug fixing.
+
+Anyway, in the case of the latest nvidia version it certainly does have 
+new features, because it supports newer cards. In this case, it's not a 
+big thing because it's relatively easy for me to install, but I would 
+think that for new users who have modern software you'd really want them 
+to have access to it. After all M2 is the latest stable release.
+
+
+
+On 20/01/13 18:03, Juan Luis Baptiste wrote:
+> On Sun, Jan 20, 2013 at 11:30 AM, Robert Wood
+> <robert.wood at apostrophe.co.uk>  wrote:
+>> Thanks for the reply, but it doesn't really make sense or seem to answer the
+>> question. I was wondering why bother with v295 when you could go for a more
+>> recent (ie most up to date) release?!
+>>
+>>
+>
+> Because of our updates policy:
+>
+> For the most part, an update should consist of a patched build of the
+> same version of the package released with the distribution, with a few
+> exceptions:
+> - Bug fix only release. There is no point in shipping all the fixes as
+> patches if the new version does not contain any new feature.
+> - Software versions that are no longer supported upstream with updates
+> (firefox and thunderbird seem to fall into this category these days)
+> - Software that is version-bound to an online service (games, virus
+> scanners?) and will only work with the latest version.
+> We will make exceptions for packages that did not make it into mga1
+> and are additions to the distribution, provided they do not impact any
+> other packages and can pass full QA.
+> Updates are not the appropriate place for packages created to satisfy
+> certain user's urges for "the latest". These types of builds belong in
+> backports.
+>
+> https://wiki.mageia.org/en/Updates_policy#Version_Policy
+>
+> New releases only go on next verson or in backports (once they're open).
+>
+> P.S.: Please don't top post next time.
+>
+>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1