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/2012-October/019171.html | 84 +++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-October/019171.html (limited to 'zarb-ml/mageia-dev/2012-October/019171.html') diff --git a/zarb-ml/mageia-dev/2012-October/019171.html b/zarb-ml/mageia-dev/2012-October/019171.html new file mode 100644 index 000000000..42b687d74 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-October/019171.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] rehashing the faac issue + + + + + + + + + +

[Mageia-dev] rehashing the faac issue

+ Frank Griffin + ftg at roadrunner.com +
+ Wed Oct 3 17:12:40 CEST 2012 +

+
+ +
On 10/03/2012 10:32 AM, Sander Lepik wrote:
+> I have one concern for that solution, how are we gonna build free 
+> packages if they can use non-free packages from the same repo. It 
+> seems technically a bit too complicated. BS would need some rewrite or 
+> we would have to rename a lot of packages that are currently in non-free.
+
+I don't understand.  If a core package is free, why would it build any 
+differently if packages it doesn't use now are present in the repo ?
+
+>
+> But on the other hand if some packages that require faac and also some 
+> package that is both in non-free and in core then how do we solve this 
+> problem? Packages in tainted probably don't use non-free as a media 
+> for buildrequires.
+
+I guess if urpmi becomes smart enough to know which license types you 
+want excluded, then it would use this same knowledge to filter 
+buildrequires.
+
+
+ + + + + + + + + + + + +
+

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