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
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
<!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=%3CAANLkTi%3DU_pgHy%2BWYzMhd5GUeoOTrBXXuAoySMk9wRa-V%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002170.html">
<LINK REL="Next" HREF="002169.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Importing RPM Spec File Syntax</H1>
<B>John Balcaen</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3CAANLkTi%3DU_pgHy%2BWYzMhd5GUeoOTrBXXuAoySMk9wRa-V%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Importing RPM Spec File Syntax">mikala at mandriva.org
</A><BR>
<I>Sat Jan 15 14:01:51 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
<LI>Next message: <A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2166">[ date ]</a>
<a href="thread.html#2166">[ thread ]</a>
<a href="subject.html#2166">[ subject ]</a>
<a href="author.html#2166">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>2011/1/15 Remy CLOUARD <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">shikamaru at mandriva.org</A>>:
><i> Hi there,
</I>Hello,
><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>
It would also be nice to add some comment inside like we're trying to do in
our kde's packaging policy (
<A HREF="http://www.mageia.org/wiki/doku.php?id=kde4_packaging_policy">http://www.mageia.org/wiki/doku.php?id=kde4_packaging_policy</A> )
aka
#
# Description:
# Forwarded:
# Bug:
# Author:
#
><i> - Buildroot changed from the original page
</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>[...]
Regarding the spec we've got at least a major difference in our kde's spec
For example not all the %define are localized at the top of the spec,especially
thoses for macro & libname : it's easier for me to have some of them in the
same part.Maybe it's due to our will massive libification, but having
more then 15
%define for macro & libname without knowing which package is affected.
Also maybe others can find useful to have the %files list for every
package listed
under their description (instead of having all of them after the
%prep,%build etc part )
Regards,
--
Balcaen John
Jabber-Id: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mikala at jabber.littleboboy.net</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
<LI>Next message: <A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2166">[ date ]</a>
<a href="thread.html#2166">[ thread ]</a>
<a href="subject.html#2166">[ subject ]</a>
<a href="author.html#2166">[ 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>
|
