diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110115/002169.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110115/002169.html | 139 |
1 files changed, 139 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110115/002169.html b/zarb-ml/mageia-dev/20110115/002169.html new file mode 100644 index 000000000..8564e8d0e --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002169.html @@ -0,0 +1,139 @@ +<!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=%3C201101151410.08259.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="002166.html"> + <LINK REL="Next" HREF="002204.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=%3C201101151410.08259.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:10:08 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2169">[ date ]</a> + <a href="thread.html#2169">[ thread ]</a> + <a href="subject.html#2169">[ subject ]</a> + <a href="author.html#2169">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 15 januari 2011 14:01:51 schreef John Balcaen: +><i> 2011/1/15 Remy CLOUARD <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">shikamaru at mandriva.org</A>>: +</I>><i> > Hi there, +</I>><i> +</I>><i> Hello, +</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> It would also be nice to add some comment inside like we're trying to do in +</I>><i> our kde's packaging policy ( +</I>><i> <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> ) +</I>><i> aka +</I>><i> # +</I>><i> # Description: +</I>><i> # Forwarded: +</I>><i> # Bug: +</I>><i> # Author: +</I>><i> # +</I> +git-svn patches have description automatically, if that format is also ok, i +see no reason why not. + +perhaps some emphasis on git-svn should be made on the wiki, relating to +patches. + +><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> [...] +</I>><i> Regarding the spec we've got at least a major difference in our kde's spec +</I>><i> For example not all the %define are localized at the top of the +</I>><i> spec,especially thoses for macro & libname : it's easier for me to have +</I>><i> some of them in the same part.Maybe it's due to our will massive +</I>><i> libification, but having more then 15 +</I>><i> %define for macro & libname without knowing which package is affected. +</I>><i> Also maybe others can find useful to have the %files list for every +</I>><i> package listed +</I>><i> under their description (instead of having all of them after the +</I>><i> %prep,%build etc part ) +</I>><i> +</I>><i> Regards, +</I> +Personally, i agree regarding the %files part to be under their respective +%description and having build stuff on the bottom part. I like that idea. + +regarding defines, i don't understand completely, but i am in favor of having +all defines up top. +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2169">[ date ]</a> + <a href="thread.html#2169">[ thread ]</a> + <a href="subject.html#2169">[ subject ]</a> + <a href="author.html#2169">[ 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> |