summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2012-April/004408.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2012-April/004408.html')
-rw-r--r--zarb-ml/mageia-sysadm/2012-April/004408.html104
1 files changed, 104 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2012-April/004408.html b/zarb-ml/mageia-sysadm/2012-April/004408.html
new file mode 100644
index 000000000..53df02eff
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2012-April/004408.html
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-sysadm] [sysadmin-commits] [2736] do not explictely set the same value as default
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5Bsysadmin-commits%5D%20%5B2736%5D%20do%20not%20explictely%09set%0A%20the%20same%20value%20as%20default&In-Reply-To=%3C1335172266.15755.2.camel%40liliana.cdg.redhat.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="004403.html">
+ <LINK REL="Next" HREF="004404.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] [sysadmin-commits] [2736] do not explictely set the same value as default</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5Bsysadmin-commits%5D%20%5B2736%5D%20do%20not%20explictely%09set%0A%20the%20same%20value%20as%20default&In-Reply-To=%3C1335172266.15755.2.camel%40liliana.cdg.redhat.com%3E"
+ TITLE="[Mageia-sysadm] [sysadmin-commits] [2736] do not explictely set the same value as default">misc at zarb.org
+ </A><BR>
+ <I>Mon Apr 23 11:11:06 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="004403.html">[Mageia-sysadm] [sysadmin-commits] [2736] do not explictely set the same value as default
+</A></li>
+ <LI>Next message: <A HREF="004404.html">[Mageia-sysadm] sucuk rebooted
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4408">[ date ]</a>
+ <a href="thread.html#4408">[ thread ]</a>
+ <a href="subject.html#4408">[ subject ]</a>
+ <a href="author.html#4408">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le dimanche 15 avril 2012 &#224; 15:01 +0200, nicolas vigier a &#233;crit :
+&gt;<i> On Sun, 15 Apr 2012, Michael Scherer wrote:
+</I>&gt;<i>
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; And for the sake of coherence, the whole repository was cleaned a few
+</I>&gt;<i> &gt; months ago to have manifests without the same boilerplate, and no one
+</I>&gt;<i> &gt; commented, and there is nothing special in repoctl to be different.
+</I>&gt;<i>
+</I>&gt;<i> I didn't see any mail on this mailing list about &quot;cleaning&quot;. It would
+</I>&gt;<i> have been nice to discuss the puppet style to use before changing
+</I>&gt;<i> the whole repository.
+</I>
+I think we all would like to have our code being reused outside of our
+infrastructure. And you are the one who try to push for a more direct
+approach of reusability, as seen by GSOC Proposal, and various mail.
+As seen in this thread, despites agreeing that sharing knowledge is a
+good thing, the exact details on how to do it are still unspecified and
+we ( as well as the whole puppet community ) didn't agree on how to do
+it, ie there is problem to solve like &quot;how to take in account different
+packages name, how to take in account different puppet version&quot;, etc.
+
+But something rather clear is that the puppet community seems to agree
+on a style guide, being recommended and followed by most people.
+
+For example, puppetlabs use this as a baseline to evaluate modules ( like on
+<A HREF="http://puppetlabs.com/blog/module-of-the-week-benoitcattienginx-basic-nginx-configuration/">http://puppetlabs.com/blog/module-of-the-week-benoitcattienginx-basic-nginx-configuration/</A> ),
+and is part of their recommendation ( <A HREF="http://puppetlabs.com/blog/writing-great-modules-an-introduction/">http://puppetlabs.com/blog/writing-great-modules-an-introduction/</A> ).
+
+( and in fact, you can often see reference to it on the blog ).
+
+So this looked to me the good thing to do, and that anyone would see the
+work ( we have commit diff for that reason ) and would ask questions if
+any.
+
+Puppet-lint also return problems that would bring issues when puppet 2.8
+will be out ( variable scoping issues ), and like any checking system,
+would be ignored if there is a endless pile of false positive, or &quot;stuff
+that we do not care&quot; ( I think that we have experimented enough with rpmlint on that
+matter, with people no longer using it until we decided to make it mandatory ).
+I also started to add a check for module name with
+a -, as this should/would be forbidden for various reasons ( ie, parser
+support it for now, but you cannot reference variable in it, and this
+would likely break with puppet 2.8 ).
+
+So cleaning seemed to be a good thing to do for all thoses reasons, and still seem.
+--
+Michael Scherer
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="004403.html">[Mageia-sysadm] [sysadmin-commits] [2736] do not explictely set the same value as default
+</A></li>
+ <LI>Next message: <A HREF="004404.html">[Mageia-sysadm] sucuk rebooted
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4408">[ date ]</a>
+ <a href="thread.html#4408">[ thread ]</a>
+ <a href="subject.html#4408">[ subject ]</a>
+ <a href="author.html#4408">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
+mailing list</a><br>
+</body></html>