diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110115/002173.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110115/002173.html | 116 |
1 files changed, 116 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110115/002173.html b/zarb-ml/mageia-dev/20110115/002173.html new file mode 100644 index 000000000..7211cc455 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002173.html @@ -0,0 +1,116 @@ +<!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=%3C201101152015.17071.anaselli%40linux.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002168.html"> + <LINK REL="Next" HREF="002171.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Importing RPM Spec File Syntax</H1> + <B>Angelo Naselli</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C201101152015.17071.anaselli%40linux.it%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">anaselli at linux.it + </A><BR> + <I>Sat Jan 15 20:15:16 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2173">[ date ]</a> + <a href="thread.html#2173">[ thread ]</a> + <a href="subject.html#2173">[ subject ]</a> + <a href="author.html#2173">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, +><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>Sorry I can't get this... I mean i'm packaging foo, the spec file +is for foo the patch is under foo svn directroy, is invoked by +foo.spec... so what's the matter in that? + +><i> * [version] is the version of the program this patch was developed +</I>><i> against, such as 1.0. +</I>hmm in a first view i seconded it, but after a while again i can't see really +why. I mean if a patch has been added into version 1.0 you can only +know when has been added not if it's still valid. +><i> 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>But here if you changed the patch because of rediffing, it's not true that is +for version 1.0, but for the new one. Otoh changing the name, means moving or +deleting-adding a new patch under svn... So again no reason to add this field +-imo of course-. +><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>Good point. That should be always asked for since the patch was added by +the packagers, but in my experienced i had packages in which passing upstream +patches was very hard if not impossible. + +><i> * [description] is a short description of the patch's purpose. +</I>iirc there is a -b option to be passed to %patch in which you can add +a string and again iirc that was used by packagers for a brief description +so +%patch0 -b string_format +is at least clear as your example +That also creates, iirc again, files used in patch with their name and +string_format suffix (e.g. foo.c -> foo.c.string_format or similar). +><i> Example: foo-1.0-fix-str-fmt.patch for a patch that fixes string format +</I>><i> errors +</I>in both cases your and mine (str-fmt and string_format) it's clear for +the one who added the patch not the one who handles the package after, +because the real point is not the patch itself but the reason of submitting it +i believe. + +Maybe some comments concerning the patch and the patch reason could be +clearer than few chars in a string name :) + +Just my thought of course :) + +Cheers, + +-- + Angelo +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 198 bytes +Desc: This is a digitally signed message part. +URL: </pipermail/mageia-dev/attachments/20110115/8bbe8206/attachment.asc> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2173">[ date ]</a> + <a href="thread.html#2173">[ thread ]</a> + <a href="subject.html#2173">[ subject ]</a> + <a href="author.html#2173">[ 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> |