diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20110115/002165.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/20110115/002165.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110115/002165.html | 107 |
1 files changed, 107 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110115/002165.html b/zarb-ml/mageia-dev/20110115/002165.html new file mode 100644 index 000000000..43a3e15c4 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002165.html @@ -0,0 +1,107 @@ +<!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=%3C201101151401.34272.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002164.html"> + <LINK REL="Next" HREF="002170.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Importing RPM Spec File Syntax</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C201101151401.34272.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Jan 15 14:01:34 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2165">[ date ]</a> + <a href="thread.html#2165">[ thread ]</a> + <a href="subject.html#2165">[ subject ]</a> + <a href="author.html#2165">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 15 januari 2011 11:08:27 schreef Remy CLOUARD: +><i> Hi there, +</I>><i> +</I>><i> I just imported the RPM Spec File Syntax page in the wiki. +</I>><i> +</I>><i> It’s located here: <A HREF="http://mageia.org/wiki/doku.php?id=spec_syntax">http://mageia.org/wiki/doku.php?id=spec_syntax</A> +</I>><i> +</I>><i> Please review this page as it’s one of the most important one for the +</I>><i> beginning of the mentoring process, with the RPM Howto page (yet to be +</I>><i> imported). +</I>><i> +</I>><i> Some comments on this page: +</I>><i> - Patch naming: +</I>><i> +</I>><i> I’m not sure we should go that far for the patch naming policy, and in +</I>><i> practice it’s not what I’ve seen up till now. +</I>><i> +</I>><i> Here’s a proposal: +</I>><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> +</I>><i> Example: foo-1.0-fix-str-fmt.patch for a patch that fixes string format +</I>><i> errors +</I>><i> +</I>><i> - Buildroot changed from the original page +</I>><i> +</I>><i> After reviewing it again, I see that some links have to be made to the +</I>><i> corresponding pages, and an explicit license should be mentionned as +</I>><i> well. +</I>><i> +</I>><i> Thanks for reviewing this page, +</I>><i> +</I>><i> Regards, +</I> + +imo, the source should be applied as well. this would allow us to find the +'next version of a patch' more easily. +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2165">[ date ]</a> + <a href="thread.html#2165">[ thread ]</a> + <a href="subject.html#2165">[ subject ]</a> + <a href="author.html#2165">[ 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> |