zarb-ml/mageia-dev/20110115/002162.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85

<!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=%3C4D3175F4.8010002%40gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="002161.html">
   <LINK REL="Next"  HREF="002164.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Importing RPM Spec File Syntax</H1>
    <B>Cazzaniga Sandro</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C4D3175F4.8010002%40gmail.com%3E"
       TITLE="[Mageia-dev] Importing RPM Spec File Syntax">cazzaniga.sandro at gmail.com
       </A><BR>
    <I>Sat Jan 15 11:24:52 CET 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
        <LI>Next message: <A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2162">[ date ]</a>
              <a href="thread.html#2162">[ thread ]</a>
              <a href="subject.html#2162">[ subject ]</a>
              <a href="author.html#2162">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le 15/01/2011 11:08, Remy CLOUARD a &#233;crit :
&gt;<i> Here&#8217;s a proposal:
</I>&gt;<i> Patches must be named in a very explicit manner to make it very clear to
</I>&gt;<i> what version it was originally applied. To that end, a patch needs to
</I>&gt;<i> follow the convention of
</I>&gt;<i> [package_name]-[version]-[description].patch:
</I>&gt;<i> 
</I>&gt;<i>   * [package_name] is the name of the package it applies against, such
</I>&gt;<i>   as 'shadow-utils' or 'gnupg'
</I>&gt;<i>   * [version] is the version of the program this patch was developed
</I>&gt;<i>   against, such as 1.0. The name of the patch should not change, even
</I>&gt;<i>   when it is rediffed, because the version allow to see in a blink since
</I>&gt;<i>   when this patch has been there. If you happen to see a patch that does
</I>&gt;<i>   not apply anymore, and rediff it, ask the package maintainer if it has
</I>&gt;<i>   been sent upstream, and why it hasn&#8217;t been merged, and send it
</I>&gt;<i>   upstream if you think it should be merged.
</I>&gt;<i>   * [description] is a short description of the patch's purpose.
</I>&gt;<i> 
</I>&gt;<i> Example: foo-1.0-fix-str-fmt.patch for a patch that fixes string format
</I>&gt;<i> errors
</I>&gt;<i> 
</I>I'm okay for naming patches as you say. It's clean and clear, we
understand well what a mistake they correspond.

-- 
Sandro Cazzaniga
IRC: Kharec (irc.freenode.net)
Twitter: @Kharec
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
	<LI>Next message: <A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#2162">[ date ]</a>
              <a href="thread.html#2162">[ thread ]</a>
              <a href="subject.html#2162">[ subject ]</a>
              <a href="author.html#2162">[ 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>