diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110117/002201.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110117/002201.html | 92 |
1 files changed, 92 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110117/002201.html b/zarb-ml/mageia-dev/20110117/002201.html new file mode 100644 index 000000000..27964bb63 --- /dev/null +++ b/zarb-ml/mageia-dev/20110117/002201.html @@ -0,0 +1,92 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Importing RPM Spec File Syntax + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C1295274833.24697.26.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002206.html"> + <LINK REL="Next" HREF="002202.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Importing RPM Spec File Syntax</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C1295274833.24697.26.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">misc at zarb.org + </A><BR> + <I>Mon Jan 17 15:33:53 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002206.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002202.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2201">[ date ]</a> + <a href="thread.html#2201">[ thread ]</a> + <a href="subject.html#2201">[ subject ]</a> + <a href="author.html#2201">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le samedi 15 janvier 2011 à 11:08 +0100, Remy CLOUARD a écrit : + +><i> Patches must be named in a very explicit manner to make it very clear to +</I>><i> what version it was originally applied. To that end, a patch needs to +</I>><i> follow the convention of +</I>><i> [package_name]-[version]-[description].patch: +</I>><i> +</I>><i> * [package_name] is the name of the package it applies against, such +</I>><i> as 'shadow-utils' or 'gnupg' +</I>><i> * [version] is the version of the program this patch was developed +</I>><i> against, such as 1.0. The name of the patch should not change, even +</I>><i> when it is rediffed, because the version allow to see in a blink since +</I>><i> when this patch has been there. If you happen to see a patch that does +</I>><i> not apply anymore, and rediff it, ask the package maintainer if it has +</I>><i> been sent upstream, and why it hasn’t been merged, and send it +</I>><i> upstream if you think it should be merged. +</I>><i> * [description] is a short description of the patch's purpose. +</I> +I would rather use comments for that : + +1) saying the patch was sent upstream, with url , or date of sending the +mail ( possibily who ) + +2) if not sent upstream, say clearly "not upstreamable because foo" + +3) if coming from upstream, link to the commit upstream + +And for people who want to sent upstream patch, iptutils is full of +patch to comment ( and so are lots of packages ). +-- +Michael Scherer + +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002206.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002202.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2201">[ date ]</a> + <a href="thread.html#2201">[ thread ]</a> + <a href="subject.html#2201">[ subject ]</a> + <a href="author.html#2201">[ 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> |