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/20110220/002692.html | 83 +++++++++++++++++++++++++++++++++ 1 file changed, 83 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110220/002692.html (limited to 'zarb-ml/mageia-dev/20110220/002692.html') diff --git a/zarb-ml/mageia-dev/20110220/002692.html b/zarb-ml/mageia-dev/20110220/002692.html new file mode 100644 index 000000000..a6206cd90 --- /dev/null +++ b/zarb-ml/mageia-dev/20110220/002692.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] About panotools patent problem (and other problematic rpms) + + + + + + + + + +

[Mageia-dev] About panotools patent problem (and other problematic rpms)

+ Philippe DIDIER + philippedidier at laposte.net +
+ Sun Feb 20 23:01:12 CET 2011 +

+
+ +
+
+>Well, the old simple logic works...
+>
+>lets say we "abuse" the release tag, for example changing "mga" >to "mgt"
+>then if the user enables "tainted" (meaning he/she wants the >rpms) urpmi
+>will automatically get the "mgt" ones, no questions asked...
+>
+>simple, and effective.
+>
+>and since the rebuild should be automatically on our bs, the >versions
+>will stay in sync.
+
+That seems to be the easyest compromise.
+Allowing to use the existing spec files from mdv and plf with the least
+modifications.
+
+2 problems indeed :
+for sysadmin point of view :
+Is the BS able to build and dispatch two different versions of the same rpm
+(core and tainted) ? 
+
+for the user
+Is the package manager able to substitue simply a tainted rpm to a core rpm
+if the tainted repos are selected ?
+
+
+
+ + + +
+

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