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 | |
| 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')
30 files changed, 3208 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110115/002153.html b/zarb-ml/mageia-dev/20110115/002153.html new file mode 100644 index 000000000..622a2fce8 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002153.html @@ -0,0 +1,82 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] taking care of some packages not maintained in Mandriva + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20taking%20care%20of%20some%20packages%20not%20maintained%20in%0A%09Mandriva&In-Reply-To=%3C201101150015.38155.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="002154.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] taking care of some packages not maintained in Mandriva</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20taking%20care%20of%20some%20packages%20not%20maintained%20in%0A%09Mandriva&In-Reply-To=%3C201101150015.38155.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] taking care of some packages not maintained in Mandriva">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Jan 15 00:15:38 CET 2011</I> + <P><UL> + + <LI>Next message: <A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2153">[ date ]</a> + <a href="thread.html#2153">[ thread ]</a> + <a href="subject.html#2153">[ subject ]</a> + <a href="author.html#2153">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op vrijdag 14 januari 2011 03:56:28 schreef Thomas Spuhler: +><i> On Thursday, January 13, 2011 12:07:43 pm Colin Guthrie wrote: +</I>><i> > 'Twas brillig, and philippe makowski at 13/01/11 18:07 did gyre and +</I>gimble: +><i> > > Hello, +</I>><i> > > +</I>><i> > > looking at <A HREF="http://maint.mandriva.com/listpkgs.php?owner=1">http://maint.mandriva.com/listpkgs.php?owner=1</A> +</I>><i> > > I saw duplicity and python-reportlab +</I>><i> > > since I don't see them yet on the svn, I'm ok too taking care of them +</I>><i> > > +</I>><i> > > I will certainly also add rubygems-fb for <A HREF="http://rubygems.org/gems/fb">http://rubygems.org/gems/fb</A> +</I>><i> > > +</I>><i> > > no objection ? +</I>><i> > +</I>><i> > I think it should be first come, first served for "no maintainer" pkgs. +</I>><i> > If a "better" maintainer steps up in the future and everyone agrees, +</I>><i> > then maintainership can be ceded later. +</I>><i> > +</I>><i> > Col +</I>><i> +</I>><i> I wonder if all packages that have a home in Mandriva will have a +</I>><i> maintainer in Mageia. +</I> +i don't think this 'll be a problem. + +Mandriva is planning on reducing packages from almost 14000 to 5000 ... + +We just need more packagers and the problem goes away :-) +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2153">[ date ]</a> + <a href="thread.html#2153">[ thread ]</a> + <a href="subject.html#2153">[ subject ]</a> + <a href="author.html#2153">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002154.html b/zarb-ml/mageia-dev/20110115/002154.html new file mode 100644 index 000000000..b8d9ac5cf --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002154.html @@ -0,0 +1,77 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Is libesd needed anymore? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Is%20libesd%20needed%20anymore%3F&In-Reply-To=%3C201101150018.31264.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="002153.html"> + <LINK REL="Next" HREF="002155.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Is libesd needed anymore?</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Is%20libesd%20needed%20anymore%3F&In-Reply-To=%3C201101150018.31264.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Is libesd needed anymore?">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Jan 15 00:18:31 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002153.html">[Mageia-dev] taking care of some packages not maintained in Mandriva +</A></li> + <LI>Next message: <A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2154">[ date ]</a> + <a href="thread.html#2154">[ thread ]</a> + <a href="subject.html#2154">[ subject ]</a> + <a href="author.html#2154">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op vrijdag 14 januari 2011 13:22:54 schreef Colin Guthrie: +><i> Hi, +</I>><i> +</I>><i> When importing packages, I'm very tempted to not import esound. It's +</I>><i> only used to compile libesd. Do we really need it? +</I>><i> +</I>><i> I don't think we ship any apps that use only esd, so I don't think +</I>><i> that's a problem but perhaps some old legacy apps (i.e. games) still +</I>><i> need it. +</I>><i> +</I>><i> What do people think? It's not really much hassle to support it, but by +</I>><i> the same token, dead projects have to be buried at some point! +</I>><i> +</I>><i> Col +</I> +I don't fully agree, dead projects can stay alive (undead). + +however, just don't import it, don't have support for it in gnome. and if +someone really needs it, he can import it and maintain it if he wants to. + +in short, drop it and let someone else figure it out at a later date. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002153.html">[Mageia-dev] taking care of some packages not maintained in Mandriva +</A></li> + <LI>Next message: <A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2154">[ date ]</a> + <a href="thread.html#2154">[ thread ]</a> + <a href="subject.html#2154">[ subject ]</a> + <a href="author.html#2154">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002155.html b/zarb-ml/mageia-dev/20110115/002155.html new file mode 100644 index 000000000..28c2653bf --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002155.html @@ -0,0 +1,89 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Is libesd needed anymore? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Is%20libesd%20needed%20anymore%3F&In-Reply-To=%3CAANLkTim%3D_eA6kkQwPdQ6udJUa6TLcJfG721igHyR1tc_%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="002154.html"> + <LINK REL="Next" HREF="002158.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Is libesd needed anymore?</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Is%20libesd%20needed%20anymore%3F&In-Reply-To=%3CAANLkTim%3D_eA6kkQwPdQ6udJUa6TLcJfG721igHyR1tc_%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Is libesd needed anymore?">ahmadsamir3891 at gmail.com + </A><BR> + <I>Sat Jan 15 00:37:53 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI>Next message: <A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2155">[ date ]</a> + <a href="thread.html#2155">[ thread ]</a> + <a href="subject.html#2155">[ subject ]</a> + <a href="author.html#2155">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 15 January 2011 01:18, Maarten Vanraes <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">maarten.vanraes at gmail.com</A>> wrote: +><i> Op vrijdag 14 januari 2011 13:22:54 schreef Colin Guthrie: +</I>>><i> Hi, +</I>>><i> +</I>>><i> When importing packages, I'm very tempted to not import esound. It's +</I>>><i> only used to compile libesd. Do we really need it? +</I>>><i> +</I>>><i> I don't think we ship any apps that use only esd, so I don't think +</I>>><i> that's a problem but perhaps some old legacy apps (i.e. games) still +</I>>><i> need it. +</I>>><i> +</I>>><i> What do people think? It's not really much hassle to support it, but by +</I>>><i> the same token, dead projects have to be buried at some point! +</I>>><i> +</I>>><i> Col +</I>><i> +</I>><i> I don't fully agree, dead projects can stay alive (undead). +</I>><i> +</I>><i> however, just don't import it, don't have support for it in gnome. and if +</I>><i> someone really needs it, he can import it and maintain it if he wants to. +</I>><i> +</I>><i> in short, drop it and let someone else figure it out at a later date. +</I>><i> +</I> +Well, no, dead projects are just that, dead... + +And if libesd is dropped all packages that BR it need to be fixed; +maybe postpone this until the importing rush is over, then it can be +phased out after this high pressure stage is over.. (just MHO). + +-- +Ahmad Samir +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI>Next message: <A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2155">[ date ]</a> + <a href="thread.html#2155">[ thread ]</a> + <a href="subject.html#2155">[ subject ]</a> + <a href="author.html#2155">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002156.html b/zarb-ml/mageia-dev/20110115/002156.html new file mode 100644 index 000000000..51d0d5a06 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002156.html @@ -0,0 +1,95 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] package import policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20package%20import%20policy&In-Reply-To=%3C201101150101.33948.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="002158.html"> + <LINK REL="Next" HREF="002159.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] package import policy</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20package%20import%20policy&In-Reply-To=%3C201101150101.33948.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] package import policy">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Jan 15 01:01:33 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI>Next message: <A HREF="002159.html">[Mageia-dev] package import policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2156">[ date ]</a> + <a href="thread.html#2156">[ thread ]</a> + <a href="subject.html#2156">[ subject ]</a> + <a href="author.html#2156">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>The wiki page lists method to import a package: +( <A HREF="http://www.mageia.org/wiki/doku.php?id=packaging">http://www.mageia.org/wiki/doku.php?id=packaging</A> ) + +so, i followed every step, then contacted my mentor, only it seems the process +is not used like that; it seems 2 ways are used; and the one used most (by +people i know) is not the one that is on the wiki page. + +So, i would like to list both on the wiki page, so it is clearer. + +this is what i would put for in between step 4 and 5 + + - a second possibility is: + - Read the [[svn-faq|FAQ]] about the new SVN + - Download the SRPM from a Mandriva Mirror. The rationale behind this is +to keep history for past changes in the RPM (there is a pre-rpm5 mdv srpm +mirror <A HREF="http://tmb.mine.nu/Mageia/Cauldron/mdv-SRPMS-pre-rpm5/">http://tmb.mine.nu/Mageia/Cauldron/mdv-SRPMS-pre-rpm5/</A> ) + - Check it does not have unlicensed Mandriva stuff: image (icons), video, +audio files, other + - Check it does have a clear, explicit license with it. + - Check software license ( free or not, existence of license file) + - Rebuild the SRPM (with bm -sl for instance) + - Import the packages with **mgarepo** import package.src.rpm. Be sure to +run this command under your ssh-agent, otherwise import will fail + - Check out the imported version in a repository with mgarepo + - Check it does not have "mandriva" / "mandrake" occurrences used as a +brand/name in the software (history/changelog is ok, emails for references are +ok) + - Update software on last stable version + - Send patches upstream if possible + - Remove useless cruft ( like macro that no longer apply ) + - Buildroot is no longer necessary + - %mdkversion + - ldconfig in post (handled by filetriggers) + - commit the update with a good commit message. + + +any objections? +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI>Next message: <A HREF="002159.html">[Mageia-dev] package import policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2156">[ date ]</a> + <a href="thread.html#2156">[ thread ]</a> + <a href="subject.html#2156">[ subject ]</a> + <a href="author.html#2156">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002157.html b/zarb-ml/mageia-dev/20110115/002157.html new file mode 100644 index 000000000..7a5f2f52a --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002157.html @@ -0,0 +1,83 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Trouble building rkhunter RPM + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Trouble%20building%20rkhunter%20RPM&In-Reply-To=%3CAANLkTin6swrgcfqTeJNXMW9E5efmaT7HJxcaRAAw4Hny%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="002163.html"> + <LINK REL="Next" HREF="002160.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Trouble building rkhunter RPM</H1> + <B>Hoyt Duff</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Trouble%20building%20rkhunter%20RPM&In-Reply-To=%3CAANLkTin6swrgcfqTeJNXMW9E5efmaT7HJxcaRAAw4Hny%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Trouble building rkhunter RPM">hoytduff at gmail.com + </A><BR> + <I>Sat Jan 15 03:41:25 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002163.html">[Mageia-dev] package import policy +</A></li> + <LI>Next message: <A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2157">[ date ]</a> + <a href="thread.html#2157">[ thread ]</a> + <a href="subject.html#2157">[ subject ]</a> + <a href="author.html#2157">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>When I originally looked at rkhunter, it was unavailable in the +Mandriva repos, or at least the ones I had enabled for the machine I +was working on at the time. I see it's in contribs. + +Oh, well . . . + +Thanks! + +On 1/14/11, Oliver Burger <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">oliver.bgr at googlemail.com</A>> wrote: +><i> Hoyt Duff <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">hoytduff at gmail.com</A>> schrieb am 2011-01-14 +</I>>><i> While I can find lots of (mostly useless) info on RPM building +</I>>><i> through Google, I'm not sure where to look for any Mandriva docs +</I>>><i> for that, so a suggestion for that would be welcome as well. +</I>><i> What about <A HREF="http://wiki.mandriva.com/en/Mandriva_RPM_HOWTO">http://wiki.mandriva.com/en/Mandriva_RPM_HOWTO</A> ? +</I>><i> +</I>><i> And one other thing: why don't you take the Mandriva src.rpm instead +</I>><i> of trying to understand the projects spec file? +</I>><i> +</I>><i> Oliver +</I>><i> +</I> + +-- +Hoyt +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002163.html">[Mageia-dev] package import policy +</A></li> + <LI>Next message: <A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2157">[ date ]</a> + <a href="thread.html#2157">[ thread ]</a> + <a href="subject.html#2157">[ subject ]</a> + <a href="author.html#2157">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002158.html b/zarb-ml/mageia-dev/20110115/002158.html new file mode 100644 index 000000000..6b661d1aa --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002158.html @@ -0,0 +1,92 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Is libesd needed anymore? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Is%20libesd%20needed%20anymore%3F&In-Reply-To=%3CAANLkTik_Xi%3Dw_zBNqBZkg1K6%2BbkX5qqPqXS6UDK_AXz5%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="002155.html"> + <LINK REL="Next" HREF="002156.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Is libesd needed anymore?</H1> + <B>Dexter Morgan</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Is%20libesd%20needed%20anymore%3F&In-Reply-To=%3CAANLkTik_Xi%3Dw_zBNqBZkg1K6%2BbkX5qqPqXS6UDK_AXz5%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Is libesd needed anymore?">dmorganec at gmail.com + </A><BR> + <I>Sat Jan 15 09:21:51 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI>Next message: <A HREF="002156.html">[Mageia-dev] package import policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2158">[ date ]</a> + <a href="thread.html#2158">[ thread ]</a> + <a href="subject.html#2158">[ subject ]</a> + <a href="author.html#2158">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Jan 15, 2011 at 12:37 AM, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +><i> On 15 January 2011 01:18, Maarten Vanraes <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">maarten.vanraes at gmail.com</A>> wrote: +</I>>><i> Op vrijdag 14 januari 2011 13:22:54 schreef Colin Guthrie: +</I>>>><i> Hi, +</I>>>><i> +</I>>>><i> When importing packages, I'm very tempted to not import esound. It's +</I>>>><i> only used to compile libesd. Do we really need it? +</I>>>><i> +</I>>>><i> I don't think we ship any apps that use only esd, so I don't think +</I>>>><i> that's a problem but perhaps some old legacy apps (i.e. games) still +</I>>>><i> need it. +</I>>>><i> +</I>>>><i> What do people think? It's not really much hassle to support it, but by +</I>>>><i> the same token, dead projects have to be buried at some point! +</I>>>><i> +</I>>>><i> Col +</I>>><i> +</I>>><i> I don't fully agree, dead projects can stay alive (undead). +</I>>><i> +</I>>><i> however, just don't import it, don't have support for it in gnome. and if +</I>>><i> someone really needs it, he can import it and maintain it if he wants to. +</I>>><i> +</I>>><i> in short, drop it and let someone else figure it out at a later date. +</I>>><i> +</I>><i> +</I>><i> Well, no, dead projects are just that, dead... +</I>><i> +</I>><i> And if libesd is dropped all packages that BR it need to be fixed; +</I>><i> maybe postpone this until the importing rush is over, then it can be +</I>><i> phased out after this high pressure stage is over.. (just MHO). +</I>><i> +</I>><i> -- +</I>><i> Ahmad Samir +</I>><i> +</I> +i think coling is right and this is the best moment to drop packages +as we won't have to rebuild anything after dropping it +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A></li> + <LI>Next message: <A HREF="002156.html">[Mageia-dev] package import policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2158">[ date ]</a> + <a href="thread.html#2158">[ thread ]</a> + <a href="subject.html#2158">[ subject ]</a> + <a href="author.html#2158">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002159.html b/zarb-ml/mageia-dev/20110115/002159.html new file mode 100644 index 000000000..8573f6da6 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002159.html @@ -0,0 +1,113 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] package import policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20package%20import%20policy&In-Reply-To=%3C20110115084842.GB4804%40shikamaru.fr%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002156.html"> + <LINK REL="Next" HREF="002163.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] package import policy</H1> + <B>Remy CLOUARD</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20package%20import%20policy&In-Reply-To=%3C20110115084842.GB4804%40shikamaru.fr%3E" + TITLE="[Mageia-dev] package import policy">shikamaru at mandriva.org + </A><BR> + <I>Sat Jan 15 09:48:42 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002156.html">[Mageia-dev] package import policy +</A></li> + <LI>Next message: <A HREF="002163.html">[Mageia-dev] package import policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2159">[ date ]</a> + <a href="thread.html#2159">[ thread ]</a> + <a href="subject.html#2159">[ subject ]</a> + <a href="author.html#2159">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Jan 15, 2011 at 01:01:33AM +0100, Maarten Vanraes wrote: +><i> The wiki page lists method to import a package: +</I>><i> ( <A HREF="http://www.mageia.org/wiki/doku.php?id=packaging">http://www.mageia.org/wiki/doku.php?id=packaging</A> ) +</I>><i> +</I>><i> so, i followed every step, then contacted my mentor, only it seems the process +</I>><i> is not used like that; it seems 2 ways are used; and the one used most (by +</I>><i> people i know) is not the one that is on the wiki page. +</I>><i> +</I>><i> So, i would like to list both on the wiki page, so it is clearer. +</I>><i> +</I>><i> this is what i would put for in between step 4 and 5 +</I>><i> +</I>><i> - a second possibility is: +</I>><i> - Read the [[svn-faq|FAQ]] about the new SVN +</I>><i> - Download the SRPM from a Mandriva Mirror. The rationale behind this is +</I>><i> to keep history for past changes in the RPM (there is a pre-rpm5 mdv srpm +</I>><i> mirror <A HREF="http://tmb.mine.nu/Mageia/Cauldron/mdv-SRPMS-pre-rpm5/">http://tmb.mine.nu/Mageia/Cauldron/mdv-SRPMS-pre-rpm5/</A> ) +</I>><i> - Check it does not have unlicensed Mandriva stuff: image (icons), video, +</I>><i> audio files, other +</I>><i> - Check it does have a clear, explicit license with it. +</I>><i> - Check software license ( free or not, existence of license file) +</I>><i> - Rebuild the SRPM (with bm -sl for instance) +</I>><i> - Import the packages with **mgarepo** import package.src.rpm. Be sure to +</I>><i> run this command under your ssh-agent, otherwise import will fail +</I>><i> - Check out the imported version in a repository with mgarepo +</I>><i> - Check it does not have "mandriva" / "mandrake" occurrences used as a +</I>><i> brand/name in the software (history/changelog is ok, emails for references are +</I>><i> ok) +</I>><i> - Update software on last stable version +</I>><i> - Send patches upstream if possible +</I>><i> - Remove useless cruft ( like macro that no longer apply ) +</I>><i> - Buildroot is no longer necessary +</I>><i> - %mdkversion +</I>><i> - ldconfig in post (handled by filetriggers) +</I>><i> - commit the update with a good commit message. +</I>><i> +</I>><i> +</I>><i> any objections? +</I>So, that means performing the import first, and then commit your changes +inside SVN. Well, I’d say why not, it would help other people review the +changes, and we would also be sure that it’s well formatted too. + +If everyone agree, I’d say we just replace the content on the wiki with +your proposal + +Regards, +-- +Rémy CLOUARD +() ascii ribbon campaign - against html e-mail +/\ www.asciiribbon.org - against proprietary attachments +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 230 bytes +Desc: not available +URL: </pipermail/mageia-dev/attachments/20110115/285757c4/attachment.asc> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002156.html">[Mageia-dev] package import policy +</A></li> + <LI>Next message: <A HREF="002163.html">[Mageia-dev] package import policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2159">[ date ]</a> + <a href="thread.html#2159">[ thread ]</a> + <a href="subject.html#2159">[ subject ]</a> + <a href="author.html#2159">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002160.html b/zarb-ml/mageia-dev/20110115/002160.html new file mode 100644 index 000000000..08b556783 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002160.html @@ -0,0 +1,114 @@ +<!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=%3C20110115100827.GD4804%40shikamaru.fr%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002157.html"> + <LINK REL="Next" HREF="002161.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Importing RPM Spec File Syntax</H1> + <B>Remy CLOUARD</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C20110115100827.GD4804%40shikamaru.fr%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">shikamaru at mandriva.org + </A><BR> + <I>Sat Jan 15 11:08:27 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A></li> + <LI>Next message: <A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2160">[ date ]</a> + <a href="thread.html#2160">[ thread ]</a> + <a href="subject.html#2160">[ subject ]</a> + <a href="author.html#2160">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi there, + +I just imported the RPM Spec File Syntax page in the wiki. + +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> + +Please review this page as it’s one of the most important one for the +beginning of the mentoring process, with the RPM Howto page (yet to be +imported). + +Some comments on this page: +- Patch naming: + +I’m not sure we should go that far for the patch naming policy, and in +practice it’s not what I’ve seen up till now. + +Here’s a proposal: +Patches must be named in a very explicit manner to make it very clear to +what version it was originally applied. To that end, a patch needs to +follow the convention of +[package_name]-[version]-[description].patch: + + * [package_name] is the name of the package it applies against, such + as 'shadow-utils' or 'gnupg' + * [version] is the version of the program this patch was developed + against, such as 1.0. The name of the patch should not change, even + when it is rediffed, because the version allow to see in a blink since + when this patch has been there. If you happen to see a patch that does + not apply anymore, and rediff it, ask the package maintainer if it has + been sent upstream, and why it hasn’t been merged, and send it + upstream if you think it should be merged. + * [description] is a short description of the patch's purpose. + +Example: foo-1.0-fix-str-fmt.patch for a patch that fixes string format +errors + +- Buildroot changed from the original page + +After reviewing it again, I see that some links have to be made to the +corresponding pages, and an explicit license should be mentionned as +well. + +Thanks for reviewing this page, + +Regards, +-- +Rémy CLOUARD +() ascii ribbon campaign - against html e-mail +/\ www.asciiribbon.org - against proprietary attachments + +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 230 bytes +Desc: not available +URL: </pipermail/mageia-dev/attachments/20110115/8203394b/attachment.asc> +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A></li> + <LI>Next message: <A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2160">[ date ]</a> + <a href="thread.html#2160">[ thread ]</a> + <a href="subject.html#2160">[ subject ]</a> + <a href="author.html#2160">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002161.html b/zarb-ml/mageia-dev/20110115/002161.html new file mode 100644 index 000000000..04b8bb6f0 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002161.html @@ -0,0 +1,109 @@ +<!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=%3C4D317321.80700%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002160.html"> + <LINK REL="Next" HREF="002162.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=%3C4D317321.80700%40gmail.com%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">cazzaniga.sandro at gmail.com + </A><BR> + <I>Sat Jan 15 11:12:49 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2161">[ date ]</a> + <a href="thread.html#2161">[ thread ]</a> + <a href="subject.html#2161">[ subject ]</a> + <a href="author.html#2161">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 15/01/2011 11:08, Remy CLOUARD a écrit : +><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>I will review this page. +I begin now. +-- +Sandro Cazzaniga +IRC: Kharec (irc.freenode.net) +Twitter: @Kharec +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2161">[ date ]</a> + <a href="thread.html#2161">[ thread ]</a> + <a href="subject.html#2161">[ subject ]</a> + <a href="author.html#2161">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002162.html b/zarb-ml/mageia-dev/20110115/002162.html new file mode 100644 index 000000000..4d60bb051 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002162.html @@ -0,0 +1,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 écrit : +><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'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> diff --git a/zarb-ml/mageia-dev/20110115/002163.html b/zarb-ml/mageia-dev/20110115/002163.html new file mode 100644 index 000000000..5eb7c9a17 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002163.html @@ -0,0 +1,124 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] package import policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20package%20import%20policy&In-Reply-To=%3C201101151356.11921.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="002159.html"> + <LINK REL="Next" HREF="002157.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] package import policy</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20package%20import%20policy&In-Reply-To=%3C201101151356.11921.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] package import policy">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Jan 15 13:56:11 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002159.html">[Mageia-dev] package import policy +</A></li> + <LI>Next message: <A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2163">[ date ]</a> + <a href="thread.html#2163">[ thread ]</a> + <a href="subject.html#2163">[ subject ]</a> + <a href="author.html#2163">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 15 januari 2011 09:48:42 schreef Remy CLOUARD: +><i> On Sat, Jan 15, 2011 at 01:01:33AM +0100, Maarten Vanraes wrote: +</I>><i> > The wiki page lists method to import a package: +</I>><i> > ( <A HREF="http://www.mageia.org/wiki/doku.php?id=packaging">http://www.mageia.org/wiki/doku.php?id=packaging</A> ) +</I>><i> > +</I>><i> > so, i followed every step, then contacted my mentor, only it seems the +</I>><i> > process is not used like that; it seems 2 ways are used; and the one +</I>><i> > used most (by people i know) is not the one that is on the wiki page. +</I>><i> > +</I>><i> > So, i would like to list both on the wiki page, so it is clearer. +</I>><i> > +</I>><i> > this is what i would put for in between step 4 and 5 +</I>><i> > +</I>><i> > - a second possibility is: +</I>><i> > - Read the [[svn-faq|FAQ]] about the new SVN +</I>><i> > - Download the SRPM from a Mandriva Mirror. The rationale behind this +</I>><i> > is +</I>><i> > +</I>><i> > to keep history for past changes in the RPM (there is a pre-rpm5 mdv srpm +</I>><i> > mirror <A HREF="http://tmb.mine.nu/Mageia/Cauldron/mdv-SRPMS-pre-rpm5/">http://tmb.mine.nu/Mageia/Cauldron/mdv-SRPMS-pre-rpm5/</A> ) +</I>><i> > +</I>><i> > - Check it does not have unlicensed Mandriva stuff: image (icons), +</I>><i> > video, +</I>><i> > +</I>><i> > audio files, other +</I>><i> > +</I>><i> > - Check it does have a clear, explicit license with it. +</I>><i> > - Check software license ( free or not, existence of license file) +</I>><i> > - Rebuild the SRPM (with bm -sl for instance) +</I>><i> > - Import the packages with **mgarepo** import package.src.rpm. Be +</I>><i> > sure to +</I>><i> > +</I>><i> > run this command under your ssh-agent, otherwise import will fail +</I>><i> > +</I>><i> > - Check out the imported version in a repository with mgarepo +</I>><i> > - Check it does not have "mandriva" / "mandrake" occurrences used as +</I>><i> > a +</I>><i> > +</I>><i> > brand/name in the software (history/changelog is ok, emails for +</I>><i> > references are ok) +</I>><i> > +</I>><i> > - Update software on last stable version +</I>><i> > - Send patches upstream if possible +</I>><i> > - Remove useless cruft ( like macro that no longer apply ) +</I>><i> > +</I>><i> > - Buildroot is no longer necessary +</I>><i> > - %mdkversion +</I>><i> > - ldconfig in post (handled by filetriggers) +</I>><i> > +</I>><i> > - commit the update with a good commit message. +</I>><i> > +</I>><i> > any objections? +</I>><i> +</I>><i> So, that means performing the import first, and then commit your changes +</I>><i> inside SVN. Well, I’d say why not, it would help other people review the +</I>><i> changes, and we would also be sure that it’s well formatted too. +</I>><i> +</I>><i> If everyone agree, I’d say we just replace the content on the wiki with +</I>><i> your proposal +</I> +No this is not a proposal. + +I'm saying that it seems to me that most people currently importing packages +at this moment seem to be using this method, instead of the method proposed on +the wiki. + +That's why i feel that i should add this (along with the other method) to the +wiki, to avoid confusion. Pending disapproval of currently active package +importers. +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002159.html">[Mageia-dev] package import policy +</A></li> + <LI>Next message: <A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2163">[ date ]</a> + <a href="thread.html#2163">[ thread ]</a> + <a href="subject.html#2163">[ subject ]</a> + <a href="author.html#2163">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002164.html b/zarb-ml/mageia-dev/20110115/002164.html new file mode 100644 index 000000000..7a549dc0f --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002164.html @@ -0,0 +1,86 @@ +<!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=%3C201101151359.42730.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="002162.html"> + <LINK REL="Next" HREF="002165.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=%3C201101151359.42730.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Jan 15 13:59:42 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2164">[ date ]</a> + <a href="thread.html#2164">[ thread ]</a> + <a href="subject.html#2164">[ subject ]</a> + <a href="author.html#2164">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 15 januari 2011 11:24:52 schreef Cazzaniga Sandro: +><i> Le 15/01/2011 11:08, Remy CLOUARD a écrit : +</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> > +</I>><i> > [package_name]-[version]-[description].patch: +</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> I'm okay for naming patches as you say. It's clean and clear, we +</I>><i> understand well what a mistake they correspond. +</I> +i disagree with the patch naming: if you rediff a patch, i assume you test it +out too, which means it was 'developped' for the current version, and i would +like people to start using this version. + +ie: rediffing is development too. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2164">[ date ]</a> + <a href="thread.html#2164">[ thread ]</a> + <a href="subject.html#2164">[ subject ]</a> + <a href="author.html#2164">[ 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> 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> diff --git a/zarb-ml/mageia-dev/20110115/002166.html b/zarb-ml/mageia-dev/20110115/002166.html new file mode 100644 index 000000000..6fa792e39 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002166.html @@ -0,0 +1,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> diff --git a/zarb-ml/mageia-dev/20110115/002167.html b/zarb-ml/mageia-dev/20110115/002167.html new file mode 100644 index 000000000..b1d367de6 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002167.html @@ -0,0 +1,108 @@ +<!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=%3C201101151402.40969.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="002204.html"> + <LINK REL="Next" HREF="002168.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=%3C201101151402.40969.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:02:40 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2167">[ date ]</a> + <a href="thread.html#2167">[ thread ]</a> + <a href="subject.html#2167">[ subject ]</a> + <a href="author.html#2167">[ 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> + +buildroot isn't removed everywhere +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2167">[ date ]</a> + <a href="thread.html#2167">[ thread ]</a> + <a href="subject.html#2167">[ subject ]</a> + <a href="author.html#2167">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002168.html b/zarb-ml/mageia-dev/20110115/002168.html new file mode 100644 index 000000000..6add678e2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002168.html @@ -0,0 +1,110 @@ +<!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=%3C201101151404.11439.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="002167.html"> + <LINK REL="Next" HREF="002173.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=%3C201101151404.11439.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:04:11 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2168">[ date ]</a> + <a href="thread.html#2168">[ thread ]</a> + <a href="subject.html#2168">[ subject ]</a> + <a href="author.html#2168">[ 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> + +i approve for macro %cleanbuildroot to be created (or to do it automagically +in %clean and %install +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2168">[ date ]</a> + <a href="thread.html#2168">[ thread ]</a> + <a href="subject.html#2168">[ subject ]</a> + <a href="author.html#2168">[ 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> 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> diff --git a/zarb-ml/mageia-dev/20110115/002170.html b/zarb-ml/mageia-dev/20110115/002170.html new file mode 100644 index 000000000..5fa4fc1c7 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002170.html @@ -0,0 +1,73 @@ +<!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=%3C20110115133713.GE4804%40shikamaru.fr%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002165.html"> + <LINK REL="Next" HREF="002166.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Importing RPM Spec File Syntax</H1> + <B>Remy CLOUARD</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C20110115133713.GE4804%40shikamaru.fr%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">shikamaru at mandriva.org + </A><BR> + <I>Sat Jan 15 14:37:13 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2170">[ date ]</a> + <a href="thread.html#2170">[ thread ]</a> + <a href="subject.html#2170">[ subject ]</a> + <a href="author.html#2170">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Jan 15, 2011 at 02:01:34PM +0100, Maarten Vanraes wrote: +><i> imo, the source should be applied as well. this would allow us to find the +</I>><i> 'next version of a patch' more easily. +</I>Well, as far as I’m concerned, I’m not a fan of overly long names. + +I think these info could be located at the top of the patch inside, like +the suggestion mikala made for describing the purpose of the patch. + +Regards, +-- +Rémy CLOUARD +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 230 bytes +Desc: not available +URL: </pipermail/mageia-dev/attachments/20110115/62b7c36e/attachment.asc> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2170">[ date ]</a> + <a href="thread.html#2170">[ thread ]</a> + <a href="subject.html#2170">[ subject ]</a> + <a href="author.html#2170">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002171.html b/zarb-ml/mageia-dev/20110115/002171.html new file mode 100644 index 000000000..f11f7f219 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002171.html @@ -0,0 +1,87 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Java-Policy first draft published + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Java-Policy%20first%20draft%20published&In-Reply-To=%3C4D31CE30.6030005%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002173.html"> + <LINK REL="Next" HREF="002172.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Java-Policy first draft published</H1> + <B>Farfouille</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Java-Policy%20first%20draft%20published&In-Reply-To=%3C4D31CE30.6030005%40laposte.net%3E" + TITLE="[Mageia-dev] Java-Policy first draft published">farfouille64 at laposte.net + </A><BR> + <I>Sat Jan 15 17:41:20 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2171">[ date ]</a> + <a href="thread.html#2171">[ thread ]</a> + <a href="subject.html#2171">[ subject ]</a> + <a href="author.html#2171">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 10/01/2011 21:56, Romain d'Alverny a écrit : +><i> +</I>><i> On Mon, Jan 10, 2011 at 21:02, Farfouille <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">farfouille64 at laposte.net</A>> wrote: +</I>>><i> Licence discrepency : dokuwiki template says licence is 'CC Attribution-Share Alike 3.0 Unported' but web application policy (<A HREF="http://mageia.org/wiki/doku.php?id=web_applications_policy">http://mageia.org/wiki/doku.php?id=web_applications_policy</A>) claims 'Creative Commons Attribution-ShareAlike 2.5 License' (end of the page) +</I>><i> +</I>><i> I used the quick admin feature of dokuwiki to set it, only the 3.0 +</I>><i> Unported was used. I have still to learn/get the differences between +</I>><i> these versions (notwithstanding that the By-SA provisions mean the +</I>><i> same thing), or whether they are even conflicting (there may be a +</I>><i> natural update path in here). +</I>><i> +</I>><i> Anyway, help/insights (separate thread, please) about this is welcome. +</I>><i> +</I>><i> Romain +</I>><i> +</I>><i> +</I>Hi, + +I browsed through 'CC Attribution-Share Alike 3.0 Unported' on <A HREF="http://creativecommons.org/licenses/by-sa/3.0/legalcode">http://creativecommons.org/licenses/by-sa/3.0/legalcode</A> +and from the hereafter section, I understand that both licences are compatible + +"You may Distribute or Publicly Perform an Adaptation only under the terms of: (i) this License; (ii) a later version of this License with the same License Elements as this License; (iii) a Creative Commons jurisdiction license (either this or a later license version) that contains the same License Elements as this License (e.g., Attribution-ShareAlike 3.0 US)); (iv) a Creative Commons Compatible License. If you license the Adaptation under one of the licenses mentioned in (iv), you must comply with the terms of that license. If you license the Adaptation under the terms of any of the licenses mentioned in (i), (ii) or (iii) (the "Applicable License"), you must comply with the terms of the Applicable License generally and the following provisions: (I) You must include a copy of, or the URI for, the Applicable License with every copy of each Adaptation You Distribute or Publicly Perform; (II) You may not offer or impose any terms on the Adaptation that restrict the terms of th +e Applicable License or the ability of the recipient of the Adaptation to exercise the rights granted to that recipient under the terms of the Applicable License; (III) You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties with every copy of the Work as included in the Adaptation You Distribute or Publicly Perform; (IV) when You Distribute or Publicly Perform the Adaptation, You may not impose any effective technological measures on the Adaptation that restrict the ability of a recipient of the Adaptation from You to exercise the rights granted to that recipient under the terms of the Applicable License. This Section 4(b) applies to the Adaptation as incorporated in a Collection, but this does not require the Collection apart from the Adaptation itself to be made subject to the terms of the Applicable License." + + +Cheers +-- +Farfouille + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2171">[ date ]</a> + <a href="thread.html#2171">[ thread ]</a> + <a href="subject.html#2171">[ subject ]</a> + <a href="author.html#2171">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002172.html b/zarb-ml/mageia-dev/20110115/002172.html new file mode 100644 index 000000000..59c0d04b2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002172.html @@ -0,0 +1,113 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Clarification on firmware licenses + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clarification%20on%20firmware%20licenses&In-Reply-To=%3C4D31EEE7.7070207%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002171.html"> + <LINK REL="Next" HREF="002174.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Clarification on firmware licenses</H1> + <B>Anssi Hannula</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clarification%20on%20firmware%20licenses&In-Reply-To=%3C4D31EEE7.7070207%40iki.fi%3E" + TITLE="[Mageia-dev] Clarification on firmware licenses">anssi.hannula at iki.fi + </A><BR> + <I>Sat Jan 15 20:00:55 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI>Next message: <A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2172">[ date ]</a> + <a href="thread.html#2172">[ thread ]</a> + <a href="subject.html#2172">[ subject ]</a> + <a href="author.html#2172">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi all! + +Sorry for bringing this stuff up again, but it seems there is still some +confusion regarding firmware licenses and to which repository put the +various firmware packages. + +Clear cases: +- open-source firmware with source code goes to core +- firmware which doesn't allow modifications or has other similar + restrictions goes to non-free + +However, what to do with firmware that is licensed under a free license +(e.g. BSD/GPL) that doesn't have source code? +There are quite a few of those (see e.g. [1]). + +A quick look at other distros shows the following: + +Debian: + - All firmware without source code goes to non-free. + - No "GPL" firmware without source code at all, even in non-free + (presumably because if Debian would distribute those files, Debian + would have to provide the source code to comply with GPL, which it + can't do because the source code isn't available at all). + - No unknown-license firmware at all. + +Fedora: + - All redistributable firmware is allowed in main repo (there is no + non-free repo), even if non-free. + - Unknown-license firmware is allowed only if it was previously + distributed as part of kernel. + +Ubuntu: + - All redistributable firmware is apparently allowed in main, even if + non-free license with restrictions on modification. (this is in + contrary to Ubuntu licensing page [2] which says that modification + must be allowed for all packages in main). + - Unknown-license firmware that was previously in kernel is also in + main. + - All other firmware files with no license at all is also allowed, + in multiverse repository. + +Mandriva: + - No sane policy, half of them is in non-free and the other half in + main. + - Unknown-license firmware is allowed only if it was previously + distributed as part of kernel. + + +[1] +<A HREF="http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob;f=WHENCE;h=d807e25c5515d05ffe5fe949b480ae661eb079fb;hb=HEAD">http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob;f=WHENCE;h=d807e25c5515d05ffe5fe949b480ae661eb079fb;hb=HEAD</A> + +[2] <A HREF="http://www.ubuntu.com/project/about-ubuntu/licensing">http://www.ubuntu.com/project/about-ubuntu/licensing</A> + +-- +Anssi Hannula +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI>Next message: <A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2172">[ date ]</a> + <a href="thread.html#2172">[ thread ]</a> + <a href="subject.html#2172">[ subject ]</a> + <a href="author.html#2172">[ 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> 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> diff --git a/zarb-ml/mageia-dev/20110115/002174.html b/zarb-ml/mageia-dev/20110115/002174.html new file mode 100644 index 000000000..67840ff3c --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002174.html @@ -0,0 +1,95 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Clarification on firmware licenses + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clarification%20on%20firmware%20licenses&In-Reply-To=%3C4D31F6BA.8030202%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002172.html"> + <LINK REL="Next" HREF="002175.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Clarification on firmware licenses</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clarification%20on%20firmware%20licenses&In-Reply-To=%3C4D31F6BA.8030202%40iki.fi%3E" + TITLE="[Mageia-dev] Clarification on firmware licenses">tmb at iki.fi + </A><BR> + <I>Sat Jan 15 20:34:18 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI>Next message: <A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2174">[ date ]</a> + <a href="thread.html#2174">[ thread ]</a> + <a href="subject.html#2174">[ subject ]</a> + <a href="author.html#2174">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Anssi Hannula skrev 15.1.2011 21:00: +><i> Hi all! +</I>><i> +</I>><i> Sorry for bringing this stuff up again, but it seems there is still some +</I>><i> confusion regarding firmware licenses and to which repository put the +</I>><i> various firmware packages. +</I>><i> +</I>><i> Clear cases: +</I>><i> - open-source firmware with source code goes to core +</I>><i> - firmware which doesn't allow modifications or has other similar +</I>><i> restrictions goes to non-free +</I>><i> +</I>><i> However, what to do with firmware that is licensed under a free license +</I>><i> (e.g. BSD/GPL) that doesn't have source code? +</I>><i> There are quite a few of those (see e.g. [1]). +</I>><i> +</I>><i> A quick look at other distros shows the following: +</I>><i> +</I>><i> Debian: +</I>><i> - All firmware without source code goes to non-free. +</I> + +This is exactly how I have planned to clean up the firmware, +but I have not had the time yet... + +So kernel-firmware (wich belongs in core) and kernel-firmware-extra +(wich belongs in nonfree) will have to be modified... + +Anything in kernel-firmware without proper license & source will be +moved to kernel-firmware-extra. + +Anything in kernel-firmware-extra with open-source firmware and source +will be moved to kernel-firmware. + +The same goes for every other firmware in the distro. + +-- +Thomas +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI>Next message: <A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2174">[ date ]</a> + <a href="thread.html#2174">[ thread ]</a> + <a href="subject.html#2174">[ subject ]</a> + <a href="author.html#2174">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002175.html b/zarb-ml/mageia-dev/20110115/002175.html new file mode 100644 index 000000000..201b8576d --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002175.html @@ -0,0 +1,92 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Clarification on firmware licenses + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clarification%20on%20firmware%20licenses&In-Reply-To=%3CAANLkTinNjSk-NF%2Bmn1Wb_3-HH4f8-0%2BCScAigdQ33WyG%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="002174.html"> + <LINK REL="Next" HREF="002176.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Clarification on firmware licenses</H1> + <B>Pascal Terjan</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clarification%20on%20firmware%20licenses&In-Reply-To=%3CAANLkTinNjSk-NF%2Bmn1Wb_3-HH4f8-0%2BCScAigdQ33WyG%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Clarification on firmware licenses">pterjan at gmail.com + </A><BR> + <I>Sat Jan 15 20:55:10 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI>Next message: <A HREF="002176.html">[Mageia-dev] mgarepo error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2175">[ date ]</a> + <a href="thread.html#2175">[ thread ]</a> + <a href="subject.html#2175">[ subject ]</a> + <a href="author.html#2175">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Jan 15, 2011 at 19:34, Thomas Backlund <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tmb at iki.fi</A>> wrote: +><i> Anssi Hannula skrev 15.1.2011 21:00: +</I>>><i> +</I>>><i> Hi all! +</I>>><i> +</I>>><i> Sorry for bringing this stuff up again, but it seems there is still some +</I>>><i> confusion regarding firmware licenses and to which repository put the +</I>>><i> various firmware packages. +</I>>><i> +</I>>><i> Clear cases: +</I>>><i> - open-source firmware with source code goes to core +</I>>><i> - firmware which doesn't allow modifications or has other similar +</I>>><i>   restrictions goes to non-free +</I>>><i> +</I>>><i> However, what to do with firmware that is licensed under a free license +</I>>><i> (e.g. BSD/GPL) that doesn't have source code? +</I>>><i> There are quite a few of those (see e.g. [1]). +</I>>><i> +</I>>><i> A quick look at other distros shows the following: +</I>>><i> +</I>>><i> Debian: +</I>>><i>  - All firmware without source code goes to non-free. +</I>><i> +</I>><i> +</I>><i> This is exactly how I have planned to clean up the firmware, +</I>><i> but I have not had the time yet... +</I>><i> +</I> +I don't agree on that. +A firmware under BSD licence is free data in my opinion whether or not +it comes with source. +On the opposite, anything under GPL without source "can't exist"... +Either we consider it is GPL and we should be able to get source if +requested and it has no reason to be in non-free, or it is not under +GPL and can not be redistributed +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + <LI>Next message: <A HREF="002176.html">[Mageia-dev] mgarepo error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2175">[ date ]</a> + <a href="thread.html#2175">[ thread ]</a> + <a href="subject.html#2175">[ subject ]</a> + <a href="author.html#2175">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002176.html b/zarb-ml/mageia-dev/20110115/002176.html new file mode 100644 index 000000000..3aed958b4 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002176.html @@ -0,0 +1,64 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mgarepo error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mgarepo%20error&In-Reply-To=%3C201101151258.10780.thomas%40btspuhler.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002175.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mgarepo error</H1> + <B>Thomas Spuhler</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mgarepo%20error&In-Reply-To=%3C201101151258.10780.thomas%40btspuhler.com%3E" + TITLE="[Mageia-dev] mgarepo error">thomas at btspuhler.com + </A><BR> + <I>Sat Jan 15 20:58:10 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2176">[ date ]</a> + <a href="thread.html#2176">[ thread ]</a> + <a href="subject.html#2176">[ subject ]</a> + <a href="author.html#2176">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I am getting this error, but the package builds + +$ mgarepo submit svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/php-sasl">ssh://svn.mageia.org/svn/packages/cauldron/php-sasl</A> -r +19483 +Implicit target: cauldron +No handlers could be found for logger "mgarepo" + + +-- +Thomas +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2176">[ date ]</a> + <a href="thread.html#2176">[ thread ]</a> + <a href="subject.html#2176">[ subject ]</a> + <a href="author.html#2176">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/002204.html b/zarb-ml/mageia-dev/20110115/002204.html new file mode 100644 index 000000000..d5fbf67de --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/002204.html @@ -0,0 +1,84 @@ +<!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=%3CAANLkTinkK45xKxOrbP%3Dfx_2U5%2B80rEgg_fyqqMLhft4f%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="002169.html"> + <LINK REL="Next" HREF="002167.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=%3CAANLkTinkK45xKxOrbP%3Dfx_2U5%2B80rEgg_fyqqMLhft4f%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">balcaen.john at gmail.com + </A><BR> + <I>Sat Jan 15 17:10:42 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2204">[ date ]</a> + <a href="thread.html#2204">[ thread ]</a> + <a href="subject.html#2204">[ subject ]</a> + <a href="author.html#2204">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>[...] +><i> regarding defines, i don't understand completely, but i am in favor of having +</I>><i> all defines up top. +</I>><i> +</I>I'm attaching two examples here : +the current kdelibs4 spec & an another one with all define @ top and +you'll probably understand why i suggest (& at least why kde's spec +are wrote as i +suggested :p ) + + +-- +Balcaen John +Jabber-Id: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mikala at jabber.littleboboy.net</A> +IRC: mikala on Freenode +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: kdelibs4.spec +Type: text/x-rpm-spec +Size: 30009 bytes +Desc: not available +URL: </pipermail/mageia-dev/attachments/20110115/2ec1b3a6/attachment-0002.bin> +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: kdelibs4-define-at-top.spec +Type: text/x-rpm-spec +Size: 30045 bytes +Desc: not available +URL: </pipermail/mageia-dev/attachments/20110115/2ec1b3a6/attachment-0003.bin> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI>Next message: <A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2204">[ date ]</a> + <a href="thread.html#2204">[ thread ]</a> + <a href="subject.html#2204">[ subject ]</a> + <a href="author.html#2204">[ 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> diff --git a/zarb-ml/mageia-dev/20110115/author.html b/zarb-ml/mageia-dev/20110115/author.html new file mode 100644 index 000000000..8faa0c194 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/author.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 15 January 2011 Archive by author</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>15 January 2011 Archives by author</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Jan 15 00:15:38 CET 2011</i><br> + <b>Ending:</b> <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Messages:</b> 25<p> + <ul> + +<LI><A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2174"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2166"> </A> +<I>John Balcaen +</I> + +<LI><A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2204"> </A> +<I>John Balcaen +</I> + +<LI><A HREF="002159.html">[Mageia-dev] package import policy +</A><A NAME="2159"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2160"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2170"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A><A NAME="2157"> </A> +<I>Hoyt Duff +</I> + +<LI><A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A><A NAME="2171"> </A> +<I>Farfouille +</I> + +<LI><A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2172"> </A> +<I>Anssi Hannula +</I> + +<LI><A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2158"> </A> +<I>Dexter Morgan +</I> + +<LI><A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2173"> </A> +<I>Angelo Naselli +</I> + +<LI><A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2155"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2161"> </A> +<I>Cazzaniga Sandro +</I> + +<LI><A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2162"> </A> +<I>Cazzaniga Sandro +</I> + +<LI><A HREF="002176.html">[Mageia-dev] mgarepo error +</A><A NAME="2176"> </A> +<I>Thomas Spuhler +</I> + +<LI><A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2175"> </A> +<I>Pascal Terjan +</I> + +<LI><A HREF="002153.html">[Mageia-dev] taking care of some packages not maintained in Mandriva +</A><A NAME="2153"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2154"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002156.html">[Mageia-dev] package import policy +</A><A NAME="2156"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002163.html">[Mageia-dev] package import policy +</A><A NAME="2163"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2164"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2165"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2167"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2168"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2169"> </A> +<I>Maarten Vanraes +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Archived on:</b> <i>Mon Jan 17 17:28:35 CET 2011</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20110115/date.html b/zarb-ml/mageia-dev/20110115/date.html new file mode 100644 index 000000000..b490ff77e --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/date.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 15 January 2011 Archive by date</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>15 January 2011 Archives by date</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Jan 15 00:15:38 CET 2011</i><br> + <b>Ending:</b> <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Messages:</b> 25<p> + <ul> + +<LI><A HREF="002153.html">[Mageia-dev] taking care of some packages not maintained in Mandriva +</A><A NAME="2153"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2154"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2155"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="002156.html">[Mageia-dev] package import policy +</A><A NAME="2156"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A><A NAME="2157"> </A> +<I>Hoyt Duff +</I> + +<LI><A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2158"> </A> +<I>Dexter Morgan +</I> + +<LI><A HREF="002159.html">[Mageia-dev] package import policy +</A><A NAME="2159"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2160"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2161"> </A> +<I>Cazzaniga Sandro +</I> + +<LI><A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2162"> </A> +<I>Cazzaniga Sandro +</I> + +<LI><A HREF="002163.html">[Mageia-dev] package import policy +</A><A NAME="2163"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2164"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2165"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2166"> </A> +<I>John Balcaen +</I> + +<LI><A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2167"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2168"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2169"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2170"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2204"> </A> +<I>John Balcaen +</I> + +<LI><A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A><A NAME="2171"> </A> +<I>Farfouille +</I> + +<LI><A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2172"> </A> +<I>Anssi Hannula +</I> + +<LI><A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2173"> </A> +<I>Angelo Naselli +</I> + +<LI><A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2174"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2175"> </A> +<I>Pascal Terjan +</I> + +<LI><A HREF="002176.html">[Mageia-dev] mgarepo error +</A><A NAME="2176"> </A> +<I>Thomas Spuhler +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Archived on:</b> <i>Mon Jan 17 17:28:35 CET 2011</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20110115/index.html b/zarb-ml/mageia-dev/20110115/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/index.html @@ -0,0 +1 @@ +thread.html
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/20110115/subject.html b/zarb-ml/mageia-dev/20110115/subject.html new file mode 100644 index 000000000..5ba58940f --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/subject.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 15 January 2011 Archive by subject</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>15 January 2011 Archives by subject</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Jan 15 00:15:38 CET 2011</i><br> + <b>Ending:</b> <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Messages:</b> 25<p> + <ul> + +<LI><A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2172"> </A> +<I>Anssi Hannula +</I> + +<LI><A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2174"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2175"> </A> +<I>Pascal Terjan +</I> + +<LI><A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2160"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2161"> </A> +<I>Cazzaniga Sandro +</I> + +<LI><A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2162"> </A> +<I>Cazzaniga Sandro +</I> + +<LI><A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2164"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2165"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2166"> </A> +<I>John Balcaen +</I> + +<LI><A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2167"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2168"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2169"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2170"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2204"> </A> +<I>John Balcaen +</I> + +<LI><A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2173"> </A> +<I>Angelo Naselli +</I> + +<LI><A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2154"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2155"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2158"> </A> +<I>Dexter Morgan +</I> + +<LI><A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A><A NAME="2171"> </A> +<I>Farfouille +</I> + +<LI><A HREF="002176.html">[Mageia-dev] mgarepo error +</A><A NAME="2176"> </A> +<I>Thomas Spuhler +</I> + +<LI><A HREF="002156.html">[Mageia-dev] package import policy +</A><A NAME="2156"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002159.html">[Mageia-dev] package import policy +</A><A NAME="2159"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002163.html">[Mageia-dev] package import policy +</A><A NAME="2163"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002153.html">[Mageia-dev] taking care of some packages not maintained in Mandriva +</A><A NAME="2153"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A><A NAME="2157"> </A> +<I>Hoyt Duff +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Archived on:</b> <i>Mon Jan 17 17:28:35 CET 2011</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20110115/thread.html b/zarb-ml/mageia-dev/20110115/thread.html new file mode 100644 index 000000000..5e2c2027e --- /dev/null +++ b/zarb-ml/mageia-dev/20110115/thread.html @@ -0,0 +1,219 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 15 January 2011 Archive by thread</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>15 January 2011 Archives by thread</h1> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Jan 15 00:15:38 CET 2011</i><br> + <b>Ending:</b> <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Messages:</b> 25<p> + <ul> + +<!--0 01295046938- --> +<LI><A HREF="002153.html">[Mageia-dev] taking care of some packages not maintained in Mandriva +</A><A NAME="2153"> </A> +<I>Maarten Vanraes +</I> + +<!--0 01295047111- --> +<LI><A HREF="002154.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2154"> </A> +<I>Maarten Vanraes +</I> + +<UL> +<!--1 01295047111-01295048273- --> +<LI><A HREF="002155.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2155"> </A> +<I>Ahmad Samir +</I> + +<UL> +<!--2 01295047111-01295048273-01295079711- --> +<LI><A HREF="002158.html">[Mageia-dev] Is libesd needed anymore? +</A><A NAME="2158"> </A> +<I>Dexter Morgan +</I> + +</UL> +</UL> +<!--0 01295049693- --> +<LI><A HREF="002156.html">[Mageia-dev] package import policy +</A><A NAME="2156"> </A> +<I>Maarten Vanraes +</I> + +<UL> +<!--1 01295049693-01295081322- --> +<LI><A HREF="002159.html">[Mageia-dev] package import policy +</A><A NAME="2159"> </A> +<I>Remy CLOUARD +</I> + +<UL> +<!--2 01295049693-01295081322-01295096171- --> +<LI><A HREF="002163.html">[Mageia-dev] package import policy +</A><A NAME="2163"> </A> +<I>Maarten Vanraes +</I> + +</UL> +</UL> +<!--0 01295059285- --> +<LI><A HREF="002157.html">[Mageia-dev] Trouble building rkhunter RPM +</A><A NAME="2157"> </A> +<I>Hoyt Duff +</I> + +<!--0 01295086107- --> +<LI><A HREF="002160.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2160"> </A> +<I>Remy CLOUARD +</I> + +<UL> +<!--1 01295086107-01295086369- --> +<LI><A HREF="002161.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2161"> </A> +<I>Cazzaniga Sandro +</I> + +<!--1 01295086107-01295087092- --> +<LI><A HREF="002162.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2162"> </A> +<I>Cazzaniga Sandro +</I> + +<UL> +<!--2 01295086107-01295087092-01295096382- --> +<LI><A HREF="002164.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2164"> </A> +<I>Maarten Vanraes +</I> + +</UL> +<!--1 01295086107-01295096494- --> +<LI><A HREF="002165.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2165"> </A> +<I>Maarten Vanraes +</I> + +<UL> +<!--2 01295086107-01295096494-01295098633- --> +<LI><A HREF="002170.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2170"> </A> +<I>Remy CLOUARD +</I> + +</UL> +<!--1 01295086107-01295096511- --> +<LI><A HREF="002166.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2166"> </A> +<I>John Balcaen +</I> + +<UL> +<!--2 01295086107-01295096511-01295097008- --> +<LI><A HREF="002169.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2169"> </A> +<I>Maarten Vanraes +</I> + +<UL> +<!--3 01295086107-01295096511-01295097008-01295107842- --> +<LI><A HREF="002204.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2204"> </A> +<I>John Balcaen +</I> + +</UL> +</UL> +<!--1 01295086107-01295096560- --> +<LI><A HREF="002167.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2167"> </A> +<I>Maarten Vanraes +</I> + +<!--1 01295086107-01295096651- --> +<LI><A HREF="002168.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2168"> </A> +<I>Maarten Vanraes +</I> + +<!--1 01295086107-01295118916- --> +<LI><A HREF="002173.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2173"> </A> +<I>Angelo Naselli +</I> + +</UL> +<!--0 01295109680- --> +<LI><A HREF="002171.html">[Mageia-dev] Java-Policy first draft published +</A><A NAME="2171"> </A> +<I>Farfouille +</I> + +<!--0 01295118055- --> +<LI><A HREF="002172.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2172"> </A> +<I>Anssi Hannula +</I> + +<UL> +<!--1 01295118055-01295120058- --> +<LI><A HREF="002174.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2174"> </A> +<I>Thomas Backlund +</I> + +<UL> +<!--2 01295118055-01295120058-01295121310- --> +<LI><A HREF="002175.html">[Mageia-dev] Clarification on firmware licenses +</A><A NAME="2175"> </A> +<I>Pascal Terjan +</I> + +</UL> +</UL> +<!--0 01295121490- --> +<LI><A HREF="002176.html">[Mageia-dev] mgarepo error +</A><A NAME="2176"> </A> +<I>Thomas Spuhler +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Jan 15 20:58:10 CET 2011</i><br> + <b>Archived on:</b> <i>Mon Jan 17 17:28:35 CET 2011</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + |