summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-January/011645.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011645.html')
-rw-r--r--zarb-ml/mageia-dev/2012-January/011645.html122
1 files changed, 122 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011645.html b/zarb-ml/mageia-dev/2012-January/011645.html
new file mode 100644
index 000000000..312fb5a26
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-January/011645.html
@@ -0,0 +1,122 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] RFC Package Naming Policy
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%20Package%20Naming%20Policy&In-Reply-To=%3C4F26E06C.3060009%40doc.ic.ac.uk%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="011675.html">
+ <LINK REL="Next" HREF="011646.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] RFC Package Naming Policy</H1>
+ <B>Pierre-Malo Deni&#233;lou</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%20Package%20Naming%20Policy&In-Reply-To=%3C4F26E06C.3060009%40doc.ic.ac.uk%3E"
+ TITLE="[Mageia-dev] RFC Package Naming Policy">malo at doc.ic.ac.uk
+ </A><BR>
+ <I>Mon Jan 30 19:24:44 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="011675.html">[Mageia-dev] stardict 3.0.3
+</A></li>
+ <LI>Next message: <A HREF="011646.html">[Mageia-dev] RFC Package Naming Policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11645">[ date ]</a>
+ <a href="thread.html#11645">[ thread ]</a>
+ <a href="subject.html#11645">[ subject ]</a>
+ <a href="author.html#11645">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Dear all,
+
+Following some recent mix-up, some possible ambiguity was found in the
+current policy with respect to package naming (as seen in
+<A HREF="https://wiki.mageia.org/en/Packaging_guidelines#Package_Naming">https://wiki.mageia.org/en/Packaging_guidelines#Package_Naming</A>).
+
+----------------------------------------------------------------------
+So currently it is written:
+&#171;* Name should be the upstream name of the software project, always
+lowercase.
+* When the package name is different to the project name, you should
+define and use %{upstream_name} macro to refer to the original project
+name within the spec
+* ''Dash '-' must be used as the delimiter for name parts.''
+* ''Do NOT use an underscore '_', a plus '+', or a period '.' as a
+delimiter.''
+* The spec file should be named using the %{name}.spec scheme, i.e. the
+name of the package should be used as the name for the spec.&#187;
+
+I propose to change it to the following:
+
+&#171;* The base package names (used for svn and src.rpm) should be the
+upstream name of the software project, always lowercase. Upstream names
+can contain digits, '+', '_' or '.', but no other special characters.
+Really exceptionally, uppercase letters can be allowed if there is
+proper justification or historical reasons.
+* Package names that are built by Mageia packagers from the upstream
+name by adding suffixes should always use '-' as delimiter (e.g.
+foo-devel or foo-plugins as derived from the foo package). All '_' and
+'+' in package names must come from upstream naming! The '.' in package
+names should only come upstream or standard versioning schemes.
+* The spec file should be named using the %{name}.spec scheme, i.e. the
+name of the source package and svn directory should be used as the name
+for the spec.&#187;
+
+---------------------------------------------------------------------
+Some of you may notice that the newly drafted policy allows upper-case
+letters in packages as an exception (when justified). This is to follow
+the current practice (which is not following the current policy, where
+we have packages like R-base).
+I don't want to raise a heated discussion (there was an inconclusive
+discussion a long time ago on cooker [*]) about enforcing an all
+lower-case policy. Not sure a consensus can be reached today, but
+lower-casing package names should be the default for 99% of the packages
+in Mageia.
+
+Any comments? Is it indeed clearer this way? Any other conditions on
+package names we should add?
+
+Best regards,
+--
+Malo
+
+[*] <A HREF="http://lists.mandriva.com/cooker/2006-03/msg03396.php">http://lists.mandriva.com/cooker/2006-03/msg03396.php</A>
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="011675.html">[Mageia-dev] stardict 3.0.3
+</A></li>
+ <LI>Next message: <A HREF="011646.html">[Mageia-dev] RFC Package Naming Policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11645">[ date ]</a>
+ <a href="thread.html#11645">[ thread ]</a>
+ <a href="subject.html#11645">[ subject ]</a>
+ <a href="author.html#11645">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>