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-February/012408.html | 98 ++++++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-February/012408.html (limited to 'zarb-ml/mageia-dev/2012-February/012408.html') diff --git a/zarb-ml/mageia-dev/2012-February/012408.html b/zarb-ml/mageia-dev/2012-February/012408.html new file mode 100644 index 000000000..ba5c10f57 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-February/012408.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release dovecot-1.2.17-3.mga2 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release dovecot-1.2.17-3.mga2

+ andre999 + andre999mga at laposte.net +
+ Mon Feb 27 21:57:49 CET 2012 +

+
+ +
Maarten Vanraes a écrit :
+> Op maandag 27 februari 2012 09:20:17 schreef Guillaume Rousse:
+>    
+>> Le 27/02/2012 08:00, Maarten Vanraes a écrit :
+>>      
+>>> Is it necessary to have these --with[out]* compile flags in the package
+>>> description?
+>>>        
+>> maybe not necessary, but definitively useful.
+>>
+>>      
+>>> maybe it'd be better to just list whatever support it has been built
+>>> with.
+>>>        
+>> It has been a standard practice for all our packages allowing
+>> conditional build options for quite a long time. Of course, this could
+>> be mentioned elsewhere as package description.
+>>      
+> i have no problem it being in the spec file, but surely a better place rather
+> than the description... it's not like users really need to know which compile
+> flags there is or what you can do with rpmbuild...
+>
+> i'm just saying this info should be moved out to comments in spec file, and
+> change the description to state what exactly is compiled in...
+>    
+It can be very useful for users to know what functions are activated in 
+a package - which the compile flags often indicate.  In the man page (or 
+other documentation) there is often reference to functions available "if 
+activated".
+So I would favour keeping compile flags in the description, if it is 
+possible that they make a difference in the functions available.
+However if the compile flags are required to make the package build 
+properly, then it does make sense to make them a comment in the spec file.
+
+My 2 cents :)
+
+-- 
+André
+
+
+ + + + + + +
+

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