diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110118')
20 files changed, 1920 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110118/002212.html b/zarb-ml/mageia-dev/20110118/002212.html new file mode 100644 index 000000000..097818f46 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002212.html @@ -0,0 +1,87 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%20protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3CAANLkTikv-so%2BS23DEfMvPeKsS8QxyOgAOEJtRhO-nzc2%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="002213.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download</H1> + <B>Per Øyvind Karlsen</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%20protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3CAANLkTikv-so%2BS23DEfMvPeKsS8QxyOgAOEJtRhO-nzc2%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download">peroyvind at mandriva.org + </A><BR> + <I>Tue Jan 18 00:06:25 CET 2011</I> + <P><UL> + + <LI>Next message: <A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2212">[ date ]</a> + <a href="thread.html#2212">[ thread ]</a> + <a href="subject.html#2212">[ subject ]</a> + <a href="author.html#2212">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2011/1/12 Marcello Anni <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">marcello.anni at alice.it</A>>: +>><i> Thanks Olivier, for saying this much better than I could +</I>>><i> +</I>>><i> wobo, yet another mirror maintainer +</I>>><i> +</I>><i> yes wobo, but  except Per Øyvind no one has really answered to my question... +</I>PS: you should really look into the research papers pointed to before +even bothering to think +about discussing this topic much further.. + +ie. to make bittorrent feasible in usage for this purpose, "regular +bittorrent" won't cut it due to numbers of +issues (ie. the common "tit for tat" - ratios put on seeding time & +data uploaded before others giving you full speed +will make bittorrent extremely slow for usage, don't forget the fact +that you'd also need for others to actually keep on seeding the +content you'd like, which for a live development distribution will be +very dynamic as well..). Using special purpose server implementations, +different DHT implementations++ will be required.. + +For large files that doesn't get frequently changed and that a lot of +people will download, "regular bittorrent" is certainly a nice thing, +but for downloading frequently changing rpms etc. you need a different +solution and a working implementation delivering this to make it of +any real use.. + +ps: sorry for my probably misleading comments on aria2 earlier, for +downloading rpms it probably wouldn't bring you much closer to that +goal as is.. + +-- +Regards, +Per Øyvind +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2212">[ date ]</a> + <a href="thread.html#2212">[ thread ]</a> + <a href="subject.html#2212">[ subject ]</a> + <a href="author.html#2212">[ 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/20110118/002213.html b/zarb-ml/mageia-dev/20110118/002213.html new file mode 100644 index 000000000..2e51c91c9 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002213.html @@ -0,0 +1,111 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Python Packaging Policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C1295308449.24697.82.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002212.html"> + <LINK REL="Next" HREF="002217.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Python Packaging Policy</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C1295308449.24697.82.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Python Packaging Policy">misc at zarb.org + </A><BR> + <I>Tue Jan 18 00:54:09 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002212.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI>Next message: <A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2213">[ date ]</a> + <a href="thread.html#2213">[ thread ]</a> + <a href="subject.html#2213">[ subject ]</a> + <a href="author.html#2213">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 17 janvier 2011 à 21:03 +0100, philippe makowski a écrit : +><i> 2011/1/17 Michael scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>>: +</I>><i> > On Sun, Jan 16, 2011 at 06:15:52PM +0100, philippe makowski wrote: +</I>><i> >> Hi, +</I>><i> >> +</I>><i> >> I though that I can find more time to work on this week end, but +</I>><i> >> unfortunately it was not the case. +</I>><i> >> +</I>><i> >> The Mandriva doc is really not a good starter +</I>><i> >> (<A HREF="http://wiki.mandriva.com/en/Python_packaging_policy">http://wiki.mandriva.com/en/Python_packaging_policy</A>) +</I>><i> > +</I>><i> > That's just a draft, but as the one that wrote the draft, could I +</I>><i> > know what is wrong with what was written so far ? +</I>><i> > +</I>><i> nothing except it is just a draft ;) +</I> +Well, i just didn't think i had the authority to impose it, nor much +time to discuss it, so I never removed the draft label. + +><i> >> so I propose to use the Fedora one +</I>><i> >> (<A HREF="http://fedoraproject.org/wiki/Packaging:Python">http://fedoraproject.org/wiki/Packaging:Python</A>) with some cleaning. +</I>><i> >> +</I>><i> >> Can we provide same macros as in In Fedora 13 and greater ? +</I>><i> >> +</I>><i> >> Do you see any major problem with the Fedora policy ? +</I>><i> > +</I>><i> > First they make plan for having more than one version of python, something +</I>><i> > that I always told I will not do since no one stepped to do much to help +</I>><i> > on the transition. In short, as long the python team will in practice be only me +</I>><i> > ( and in practice, I mean "people who effectivly commit" ), we will have only 1 supported +</I>><i> > version of the stack. +</I>><i> > ( I consider python 3 to be a different language, because of the +</I>><i> > source level incompatibility ). +</I>><i> > +</I>><i> > There is also the issue on bytecompilation ( <A HREF="https://qa.mandriva.com/show_bug.cgi?id=50484">https://qa.mandriva.com/show_bug.cgi?id=50484</A> ). +</I>><i> > I have exposed there the various problem, and apart from explaining +</I>><i> > that the solution I chosed was not better than the other, no one gave a compeling +</I>><i> > argument into one or the others alternatives. +</I>><i> > +</I>><i> > Finally, a vast part of the policy is handling 2to3, a topic that we didn't discuss +</I>><i> > at all, and I would not be confortable to adopt it without first looking at it and +</I>><i> > discussing it. +</I>><i> > +</I>><i> > Not to mention that our policy draft speak of thing they do not include +</I>><i> > ( like naming policy, for a start ). +</I>><i> > +</I>><i> No problem, I understand perfectly +</I>><i> so let start with the Mandriva draft +</I> +We can merge part of their policy , I am not against it, I just think we +should not adopt everything :) +-- +Michael Scherer + +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002212.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI>Next message: <A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2213">[ date ]</a> + <a href="thread.html#2213">[ thread ]</a> + <a href="subject.html#2213">[ subject ]</a> + <a href="author.html#2213">[ 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/20110118/002214.html b/zarb-ml/mageia-dev/20110118/002214.html new file mode 100644 index 000000000..06dab339f --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002214.html @@ -0,0 +1,82 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Compatibility: %mdkversion macro? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Compatibility%3A%20%25mdkversion%20macro%3F&In-Reply-To=%3C201101171807.32326.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="002217.html"> + <LINK REL="Next" HREF="002215.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Compatibility: %mdkversion macro?</H1> + <B>Thomas Spuhler</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Compatibility%3A%20%25mdkversion%20macro%3F&In-Reply-To=%3C201101171807.32326.thomas%40btspuhler.com%3E" + TITLE="[Mageia-dev] Compatibility: %mdkversion macro?">thomas at btspuhler.com + </A><BR> + <I>Tue Jan 18 02:07:32 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI>Next message: <A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2214">[ date ]</a> + <a href="thread.html#2214">[ thread ]</a> + <a href="subject.html#2214">[ subject ]</a> + <a href="author.html#2214">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Monday, January 17, 2011 11:45:24 am Maarten Vanraes wrote: +><i> Op maandag 17 januari 2011 18:23:55 schreef Thierry Vignaud: +</I>><i> > On 17 January 2011 16:58, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote: +</I>><i> > >> Given the fact that rpm5 is drifting away from the usage of %mkrel for +</I>><i> > >> using %distepoch, I truly doubt this will happen. +</I>><i> > > +</I>><i> > > I think the mkrels will stay for a while tho' (for ease of backporting) +</I>><i> > > so I think we'll have some "breathing space" in this regard. I suspect +</I>><i> > > that once all the wrinkles are ironed out, that we'll also go down the +</I>><i> > > RPM5 route (which will hopefully be easier for us then), in which case +</I>><i> > > the distepoch will likely become used by us too. +</I>><i> > +</I>><i> > what for? +</I>><i> > I would rather stick with other mainstream rpm-based distro and remain +</I>><i> > with rpm.org +</I>><i> +</I>><i> i would as well, however, it might be that rpm5 will become mainstream +</I>><i> later on. However, i do think we should agree on using rpm.org until such +</I>><i> a time that rpm5 is stable by other rpm-based distro's +</I>><i> +</I>><i> personally, i would like some new features, and i'm prepared to work on it; +</I>><i> so I might help with maintaining current rpm. +</I>Wouldn't then our rpm not be compatible with anybody else? +-- +Thomas +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI>Next message: <A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2214">[ date ]</a> + <a href="thread.html#2214">[ thread ]</a> + <a href="subject.html#2214">[ subject ]</a> + <a href="author.html#2214">[ 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/20110118/002215.html b/zarb-ml/mageia-dev/20110118/002215.html new file mode 100644 index 000000000..d26557e5c --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002215.html @@ -0,0 +1,89 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Compatibility: %mdkversion macro? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Compatibility%3A%20%25mdkversion%20macro%3F&In-Reply-To=%3C201101180824.19570.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="002214.html"> + <LINK REL="Next" HREF="002216.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Compatibility: %mdkversion macro?</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Compatibility%3A%20%25mdkversion%20macro%3F&In-Reply-To=%3C201101180824.19570.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Compatibility: %mdkversion macro?">maarten.vanraes at gmail.com + </A><BR> + <I>Tue Jan 18 08:24:19 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2215">[ date ]</a> + <a href="thread.html#2215">[ thread ]</a> + <a href="subject.html#2215">[ subject ]</a> + <a href="author.html#2215">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op dinsdag 18 januari 2011 02:07:32 schreef Thomas Spuhler: +><i> On Monday, January 17, 2011 11:45:24 am Maarten Vanraes wrote: +</I>><i> > Op maandag 17 januari 2011 18:23:55 schreef Thierry Vignaud: +</I>><i> > > On 17 January 2011 16:58, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote: +</I>><i> > > >> Given the fact that rpm5 is drifting away from the usage of %mkrel +</I>><i> > > >> for using %distepoch, I truly doubt this will happen. +</I>><i> > > > +</I>><i> > > > I think the mkrels will stay for a while tho' (for ease of +</I>><i> > > > backporting) so I think we'll have some "breathing space" in this +</I>><i> > > > regard. I suspect that once all the wrinkles are ironed out, that +</I>><i> > > > we'll also go down the RPM5 route (which will hopefully be easier +</I>><i> > > > for us then), in which case the distepoch will likely become used by +</I>><i> > > > us too. +</I>><i> > > +</I>><i> > > what for? +</I>><i> > > I would rather stick with other mainstream rpm-based distro and remain +</I>><i> > > with rpm.org +</I>><i> > +</I>><i> > i would as well, however, it might be that rpm5 will become mainstream +</I>><i> > later on. However, i do think we should agree on using rpm.org until such +</I>><i> > a time that rpm5 is stable by other rpm-based distro's +</I>><i> > +</I>><i> > personally, i would like some new features, and i'm prepared to work on +</I>><i> > it; so I might help with maintaining current rpm. +</I>><i> +</I>><i> Wouldn't then our rpm not be compatible with anybody else? +</I> +afaik every distro uses rpm with different patches and extra features. but i +can be wrong. + +In any case, there are some thing like the automatic dependency chooser which +can improve (no change to spec files), and things like that... +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2215">[ date ]</a> + <a href="thread.html#2215">[ thread ]</a> + <a href="subject.html#2215">[ subject ]</a> + <a href="author.html#2215">[ 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/20110118/002216.html b/zarb-ml/mageia-dev/20110118/002216.html new file mode 100644 index 000000000..5ea3b1a6b --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002216.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%09protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C4D354094.6070407%40animeneko.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002215.html"> + <LINK REL="Next" HREF="002219.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download</H1> + <B>Motoko-chan</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%09protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C4D354094.6070407%40animeneko.net%3E" + TITLE="[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download">motokochan at animeneko.net + </A><BR> + <I>Tue Jan 18 08:26:12 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2216">[ date ]</a> + <a href="thread.html#2216">[ thread ]</a> + <a href="subject.html#2216">[ subject ]</a> + <a href="author.html#2216">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +><i> However I feel that +</I>><i> 4) It is reasonable for downloaders to use multiple connexions per +</I>><i> mirror, as long as they don't bypass the controls put in place by the +</I>><i> mirror. Not only reasonable, but actually desirable in terms of using +</I>><i> otherwise unused download capacity that occurs from time to time, and +</I>><i> thus enhancing general download access. +</I> +This method only works in the following situations: + +- The mirror limits the speed of each individual connection +- You use multiple mirrors to download +- If applying to a single file across multiple mirrors, the mirrors +support transfer of selective portions of the requested file + +In the first situation, the mirror maintainer usually has a good reason +for limiting connection speed. If their limit is very low, you should +contact the project they are mirroring and suggest they be dropped as an +official mirror. Going around admin-imposed limitations is bad manners +at the very least and will either get you banned or cause further +restrictions that will harm everyone. + +In the second situation, you are now taking the bandwidth of multiple +mirrors, increasing the overall load on the mirror network. Use of four +mirrors means you just took up resources that three other people could +have been using. Effectively, you're being greedy to the detriment of +the community. + +The third situation presumes a certain configuration that isn't +necessarily true. It also has the same problems as the second situation. + +><i> +</I>><i> There is another factor that may not have been considered. Many +</I>><i> downloaders will be slowed by their internet access or other +</I>><i> non-mirror factors, which will very much increase the likelihood that +</I>><i> mirrors have unused bandwidth at various times. Increasing the +</I>><i> utility -- from both sides -- of multiple connexions. +</I> +That is an argument against multi-mirror downloads. Most mirror servers +will have good bandwidth for their region. In general, the user's +connection will be a bottleneck. The overhead of maintaining multiple +connections can actually _slow down_ the downloads. + +As for torrents, there exists a large problem in that there are several +ways to handle such things (torrent per file, torrent per directory, +etc) and on every change you would need the torrent to be regenerated +and seeds to be established. If you are doing this on something with a +lot of file churn such as a development trunk, you run into a ton of +management overhead for handling the torrents. Even if you start with +web seeds, you now strain your mirrors by requesting that they be active +in seeding a bunch of torrents. + +Bittorrent makes good sense in one big situation: you have a single +large or multiple files that will be widely downloaded and distributed, +and the downloaders are likely to leave their download tool (torrent +application) running after download. This is especially useful when it's +going to be a large, but temporary, demand such as ISO files at release +time. While some mirrors might be able to handle a 200-300% increase in +traffic, others may not. It's expensive to provision at that capacity +when such a thing only happens twice a year for a week or maybe two. In +such cases, torrents make very good sense as they help reduce the peak +demand on your mirrors. + + - Michael +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI>Next message: <A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2216">[ date ]</a> + <a href="thread.html#2216">[ thread ]</a> + <a href="subject.html#2216">[ subject ]</a> + <a href="author.html#2216">[ 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/20110118/002217.html b/zarb-ml/mageia-dev/20110118/002217.html new file mode 100644 index 000000000..a4b202ec5 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002217.html @@ -0,0 +1,60 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Python Packaging Policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3CAANLkTi%3DC7s1DaLuW43-7JEE9EycC_iw4pw75UsRH%3DZYB%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="002213.html"> + <LINK REL="Next" HREF="002214.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Python Packaging Policy</H1> + <B>philippe makowski</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3CAANLkTi%3DC7s1DaLuW43-7JEE9EycC_iw4pw75UsRH%3DZYB%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Python Packaging Policy">makowski.mageia at gmail.com + </A><BR> + <I>Tue Jan 18 08:39:03 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI>Next message: <A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2217">[ date ]</a> + <a href="thread.html#2217">[ thread ]</a> + <a href="subject.html#2217">[ subject ]</a> + <a href="author.html#2217">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2011/1/18 Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>>: +><i> We can merge part of their policy , I am not against it, I just think we +</I>><i> should not adopt everything :) +</I>Fine +So I'll try to +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI>Next message: <A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2217">[ date ]</a> + <a href="thread.html#2217">[ thread ]</a> + <a href="subject.html#2217">[ subject ]</a> + <a href="author.html#2217">[ 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/20110118/002218.html b/zarb-ml/mageia-dev/20110118/002218.html new file mode 100644 index 000000000..752ef3c9d --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002218.html @@ -0,0 +1,62 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mailing list for new RPMs + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mailing%20list%20for%20new%20RPMs&In-Reply-To=%3CAANLkTi%3DnG7XyVrejLta%3DsEAfP0Lwf_9rDWQ7vLxt1pAm%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="002219.html"> + <LINK REL="Next" HREF="002220.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mailing list for new RPMs</H1> + <B>Thierry Vignaud</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mailing%20list%20for%20new%20RPMs&In-Reply-To=%3CAANLkTi%3DnG7XyVrejLta%3DsEAfP0Lwf_9rDWQ7vLxt1pAm%40mail.gmail.com%3E" + TITLE="[Mageia-dev] mailing list for new RPMs">thierry.vignaud at gmail.com + </A><BR> + <I>Tue Jan 18 08:46:14 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI>Next message: <A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2218">[ date ]</a> + <a href="thread.html#2218">[ thread ]</a> + <a href="subject.html#2218">[ subject ]</a> + <a href="author.html#2218">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi + +Could we set up a mailing list for new uploaded RPMs like we had in Mandriva? + +See you +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI>Next message: <A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2218">[ date ]</a> + <a href="thread.html#2218">[ thread ]</a> + <a href="subject.html#2218">[ subject ]</a> + <a href="author.html#2218">[ 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/20110118/002219.html b/zarb-ml/mageia-dev/20110118/002219.html new file mode 100644 index 000000000..41ca71d19 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002219.html @@ -0,0 +1,171 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%09protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C4D355138.9020107%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002216.html"> + <LINK REL="Next" HREF="002218.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20Mageia%3A%20implement%20bitorrent%09protocol%0A%20to%20allow%20updates%20download&In-Reply-To=%3C4D355138.9020107%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download">andr55 at laposte.net + </A><BR> + <I>Tue Jan 18 09:37:12 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI>Next message: <A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2219">[ date ]</a> + <a href="thread.html#2219">[ thread ]</a> + <a href="subject.html#2219">[ subject ]</a> + <a href="author.html#2219">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Motoko-chan a écrit : +><i> +</I>><i> +</I>>><i> However I feel that +</I>>><i> 4) It is reasonable for downloaders to use multiple connexions per +</I>>><i> mirror, as long as they don't bypass the controls put in place by the +</I>>><i> mirror. Not only reasonable, but actually desirable in terms of using +</I>>><i> otherwise unused download capacity that occurs from time to time, and +</I>>><i> thus enhancing general download access. +</I>><i> +</I>><i> This method only works in the following situations: +</I>><i> +</I>><i> - The mirror limits the speed of each individual connection +</I>><i> - You use multiple mirrors to download +</I>><i> - If applying to a single file across multiple mirrors, the mirrors +</I>><i> support transfer of selective portions of the requested file +</I>><i> +</I>><i> In the first situation, the mirror maintainer usually has a good reason +</I>><i> for limiting connection speed. If their limit is very low, you should +</I>><i> contact the project they are mirroring and suggest they be dropped as an +</I>><i> official mirror. Going around admin-imposed limitations is bad manners +</I>><i> at the very least and will either get you banned or cause further +</I>><i> restrictions that will harm everyone. +</I> +Many mirror sites do restrict multiple connexions (per user), so +evidently it is readily done. If a mirror chooses not to make such +restrictions, that is their choice. It is not good form (to put it +mildly) for some mirrors to try to dictate mirror policy for other +mirrors, which could have different interests. +Limiting the connexion speed could be an easy way to ensure that usually +everyone who wishes to connect can do so in busy times. In less busy +times, multiple connexions to such mirrors causes no problem. +Software such as aria2c monitors the download speed of connexions, and +will avoid slower connexions, thus balancing use of available download +ressources between mirrors. + +><i> In the second situation, you are now taking the bandwidth of multiple +</I>><i> mirrors, increasing the overall load on the mirror network. Use of four +</I>><i> mirrors means you just took up resources that three other people could +</I>><i> have been using. Effectively, you're being greedy to the detriment of +</I>><i> the community. +</I> +So for 2 hours one uses 4x download ressources instead of 8 hours of x +download ressources. In both cases using 8x ressources. +A simple elementary school calculation. +For large files, such as ISOs, it makes a big different to the user. +Globally, it makes no difference collectively to the mirrors. Except +that downloading will tend to be balanced between mirrors if software +such as aria2c is used. And mirrors with free download ressources are +more likely to be more fully used. +(One could always quibble about the overhead per connexion, but that is +relatively minor compared to the download itself.) + +><i> The third situation presumes a certain configuration that isn't +</I>><i> necessarily true. It also has the same problems as the second situation. +</I> +The third case is generally true for ftp mirrors, as well as many http +mirrors. Where it is not, aria2c and similar software will not use the +mirror. + +Don't forget that the major target of multiple connexions will be the +larger/faster mirrors, thus taking load off smaller mirrors. (Since +applications like aria2c favour faster connexions.) + +>><i> There is another factor that may not have been considered. Many +</I>>><i> downloaders will be slowed by their internet access or other +</I>>><i> non-mirror factors, which will very much increase the likelihood that +</I>>><i> mirrors have unused bandwidth at various times. Increasing the utility +</I>>><i> -- from both sides -- of multiple connexions. +</I>><i> +</I>><i> That is an argument against multi-mirror downloads. Most mirror servers +</I>><i> will have good bandwidth for their region. In general, the user's +</I>><i> connection will be a bottleneck. The overhead of maintaining multiple +</I>><i> connections can actually _slow down_ the downloads. +</I> +So you believe that unused download bandwith should not be used ? +Sounds like that would _really_ help downloaders -- and other mirrors. + +Among the potential non-mirror factors which could limit the download +speed is the capacity of the download path. Multiple connexions spread +the download over multiple paths, minimising this potential bottleneck. + +><i> As for torrents, there exists a large problem in that there are several +</I>><i> ways to handle such things (torrent per file, torrent per directory, +</I>><i> etc) and on every change you would need the torrent to be regenerated +</I>><i> and seeds to be established. If you are doing this on something with a +</I>><i> lot of file churn such as a development trunk, you run into a ton of +</I>><i> management overhead for handling the torrents. Even if you start with +</I>><i> web seeds, you now strain your mirrors by requesting that they be active +</I>><i> in seeding a bunch of torrents. +</I>><i> +</I>><i> Bittorrent makes good sense in one big situation: you have a single +</I>><i> large or multiple files that will be widely downloaded and distributed, +</I>><i> and the downloaders are likely to leave their download tool (torrent +</I>><i> application) running after download. This is especially useful when it's +</I>><i> going to be a large, but temporary, demand such as ISO files at release +</I>><i> time. While some mirrors might be able to handle a 200-300% increase in +</I>><i> traffic, others may not. It's expensive to provision at that capacity +</I>><i> when such a thing only happens twice a year for a week or maybe two. In +</I>><i> such cases, torrents make very good sense as they help reduce the peak +</I>><i> demand on your mirrors. +</I> +Evidently you understand the bittorent issue. +Note that it is essentially those with faster download/upload speeds +that act as secondary mirrors that provide the benefit. Many users +can't offer that. +Interesting that you acknowlege the variation in demand in discussing +bittorent. Which implies that some capacity is not always used. Which +applies to the multiple connexion issue. + +><i> - Michael +</I> +Regards :) + +-- +André +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A></li> + <LI>Next message: <A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2219">[ date ]</a> + <a href="thread.html#2219">[ thread ]</a> + <a href="subject.html#2219">[ subject ]</a> + <a href="author.html#2219">[ 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/20110118/002220.html b/zarb-ml/mageia-dev/20110118/002220.html new file mode 100644 index 000000000..1a55835c6 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002220.html @@ -0,0 +1,76 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mailing list for new RPMs + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mailing%20list%20for%20new%20RPMs&In-Reply-To=%3C4D3599B9.1020402%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002218.html"> + <LINK REL="Next" HREF="002224.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mailing list for new RPMs</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mailing%20list%20for%20new%20RPMs&In-Reply-To=%3C4D3599B9.1020402%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] mailing list for new RPMs">mageia at colin.guthr.ie + </A><BR> + <I>Tue Jan 18 14:46:33 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2220">[ date ]</a> + <a href="thread.html#2220">[ thread ]</a> + <a href="subject.html#2220">[ subject ]</a> + <a href="author.html#2220">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Thierry Vignaud at 18/01/11 07:46 did gyre and gimble: +><i> Could we set up a mailing list for new uploaded RPMs like we had in Mandriva? +</I> +... and register it on GMane.org :) + +Col + +-- + +Colin Guthrie +mageia(at)colin.guthr.ie +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited [<A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>] +Open Source: + Mageia Contributor [<A HREF="http://www.mageia.org/">http://www.mageia.org/</A>] + PulseAudio Hacker [<A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>] + Trac Hacker [<A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>] +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2220">[ date ]</a> + <a href="thread.html#2220">[ thread ]</a> + <a href="subject.html#2220">[ subject ]</a> + <a href="author.html#2220">[ 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/20110118/002221.html b/zarb-ml/mageia-dev/20110118/002221.html new file mode 100644 index 000000000..14c404213 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002221.html @@ -0,0 +1,111 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proofreading web applications policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C20110118180700.GA14361%40shikamaru.fr%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002316.html"> + <LINK REL="Next" HREF="002222.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proofreading web applications policy</H1> + <B>Remy CLOUARD</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C20110118180700.GA14361%40shikamaru.fr%3E" + TITLE="[Mageia-dev] Proofreading web applications policy">shikamaru at mandriva.org + </A><BR> + <I>Tue Jan 18 19:07:00 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A></li> + <LI>Next message: <A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2221">[ date ]</a> + <a href="thread.html#2221">[ thread ]</a> + <a href="subject.html#2221">[ subject ]</a> + <a href="author.html#2221">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello there, + +I started to have a look at the webapps policy. + +There’s something that has been bugging me for a while, that’s the +apache-centric way of thinking of this policy. + +To me, there are valuable alternatives to apache that deserve to be +treated equally. +Here are the packages that provides webserver + +apache-ssl|apache-mpm-event|apache-mpm-peruser|nginx|lighttpd| +cherokee|apache-mpm-itk|apache-mpm-worker|thttpd|apache-mpm-rsbac| +apache-mpm-prefork|boa + +“These are the files that are susceptible to change during the +application's lifetime. They go in /var/lib/foo. If they are supposed to +be editable by the application directly from the web interface, they +should be owned by apache user and apache group.” + +Could we create a generic group (webserver for instance) to allow +webapps to play nice with these webserver ? + +Same goes for logfiles and config files containing sensitive +informations. + +I would also be in favor of creating subpackages for webapps that +provides better integration with apache such as files in +/etc/httpd/conf/webapps.d/. + +That way, webapps should have a Requires on webserver, and the +subpackage should have one on apache. + +Another issue is the owner of /var/www. This directory is owned by +apache-conf. Could we instead make a generic package called +webserver-data for instance that would provide it ? This way each +package providing webserver would have to require webserver-data. + +Finally, that may be a little cosmetic detail, but I would prefer +template files for apache to be in a separate file in SOURCES/ that’s +included instead of creating it in the spec like: +cat > %{buildroot}%{_webappconfdir}/%{name}.conf <<EOF +-- +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/20110118/d03ff77a/attachment.asc> +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A></li> + <LI>Next message: <A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2221">[ date ]</a> + <a href="thread.html#2221">[ thread ]</a> + <a href="subject.html#2221">[ subject ]</a> + <a href="author.html#2221">[ 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/20110118/002222.html b/zarb-ml/mageia-dev/20110118/002222.html new file mode 100644 index 000000000..cfcf91c22 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002222.html @@ -0,0 +1,120 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proofreading web applications policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C201101181948.04290.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="002221.html"> + <LINK REL="Next" HREF="002223.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proofreading web applications policy</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C201101181948.04290.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Proofreading web applications policy">maarten.vanraes at gmail.com + </A><BR> + <I>Tue Jan 18 19:48:04 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI>Next message: <A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2222">[ date ]</a> + <a href="thread.html#2222">[ thread ]</a> + <a href="subject.html#2222">[ subject ]</a> + <a href="author.html#2222">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op dinsdag 18 januari 2011 19:07:00 schreef Remy CLOUARD: +><i> Hello there, +</I>><i> +</I>><i> I started to have a look at the webapps policy. +</I>><i> +</I>><i> There’s something that has been bugging me for a while, that’s the +</I>><i> apache-centric way of thinking of this policy. +</I>><i> +</I>><i> To me, there are valuable alternatives to apache that deserve to be +</I>><i> treated equally. +</I>><i> Here are the packages that provides webserver +</I>><i> +</I>><i> apache-ssl|apache-mpm-event|apache-mpm-peruser|nginx|lighttpd| +</I>><i> cherokee|apache-mpm-itk|apache-mpm-worker|thttpd|apache-mpm-rsbac| +</I>><i> apache-mpm-prefork|boa +</I>><i> +</I>><i> “These are the files that are susceptible to change during the +</I>><i> application's lifetime. They go in /var/lib/foo. If they are supposed to +</I>><i> be editable by the application directly from the web interface, they +</I>><i> should be owned by apache user and apache group.” +</I>><i> +</I>><i> Could we create a generic group (webserver for instance) to allow +</I>><i> webapps to play nice with these webserver ? +</I> +i think we could call it www-data so we can play nice in multidistro +environment with idmapping (or possibly even no idmapping). + +><i> Same goes for logfiles and config files containing sensitive +</I>><i> informations. +</I>><i> +</I>><i> I would also be in favor of creating subpackages for webapps that +</I>><i> provides better integration with apache such as files in +</I>><i> /etc/httpd/conf/webapps.d/. +</I> +i'm in favor of webapps that are webserver independant. + +><i> That way, webapps should have a Requires on webserver, and the +</I>><i> subpackage should have one on apache. +</I>><i> +</I>><i> Another issue is the owner of /var/www. This directory is owned by +</I>><i> apache-conf. Could we instead make a generic package called +</I>><i> webserver-data for instance that would provide it ? This way each +</I>><i> package providing webserver would have to require webserver-data. +</I> +www-data ? again? + +><i> Finally, that may be a little cosmetic detail, but I would prefer +</I>><i> template files for apache to be in a separate file in SOURCES/ that’s +</I>><i> included instead of creating it in the spec like: +</I>><i> cat > %{buildroot}%{_webappconfdir}/%{name}.conf <<EOF +</I> +agreed + + +One more thing, for apache specific: apache has multiple layouts, and the +current redhat-like one (or even mandriva-one) is not really that easy to +configure. the debian-style layout with vhosting on by default is much easier +imho. (perhaps vhosting by default could be something that all webservers are +set up on.) + +However, this is all great, but we agreed to have mandriva-2010.2 upgrade +paths. so don't forget about that. +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI>Next message: <A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2222">[ date ]</a> + <a href="thread.html#2222">[ thread ]</a> + <a href="subject.html#2222">[ subject ]</a> + <a href="author.html#2222">[ 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/20110118/002223.html b/zarb-ml/mageia-dev/20110118/002223.html new file mode 100644 index 000000000..ac05d49cc --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002223.html @@ -0,0 +1,82 @@ +<!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=%3C4D35E314.8020007%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002222.html"> + <LINK REL="Next" HREF="002225.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Importing RPM Spec File Syntax</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Importing%20RPM%20Spec%20File%20Syntax&In-Reply-To=%3C4D35E314.8020007%40arcor.de%3E" + TITLE="[Mageia-dev] Importing RPM Spec File Syntax">doktor5000 at arcor.de + </A><BR> + <I>Tue Jan 18 19:59:32 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI>Next message: <A HREF="002225.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2223">[ date ]</a> + <a href="thread.html#2223">[ thread ]</a> + <a href="subject.html#2223">[ subject ]</a> + <a href="author.html#2223">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Am 17.01.2011 23:50, schrieb Per Øyvind Karlsen: +><i> 2011/1/17 Florian Hubold<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">doktor5000 at arcor.de</A>>: +</I>>><i> I have one comment, or more of a question: Why is it that some time ago +</I>>><i> there used to be this syntax as de-facto standard: +</I>>><i> +</I>>><i> %define name +</I>>><i> Name: %name +</I>>><i> +</I>>><i> Never understood this, so i went with what seems the new standard, +</I>>><i> which saves you at least 3 lines per spec and improving readability. +</I>>><i> +</I>>><i> So anyone can enlighten me why name, release and version had %defines? +</I>><i> Legacy practice which got stuck with some... +</I>><i> +</I>><i> 'Name: foo' will always define %{name} now (which has been the case for ages), +</I>><i> so there's no longer use in doing this anymore. +</I>><i> It mainly adds unnecessary obscurity and confusion, please just drop this. +</I>><i> +</I>><i> -- +</I>><i> Regards, +</I>><i> Per Øyvind +</I>><i> +</I>Thanks for the info, just what i thought. + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI>Next message: <A HREF="002225.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2223">[ date ]</a> + <a href="thread.html#2223">[ thread ]</a> + <a href="subject.html#2223">[ subject ]</a> + <a href="author.html#2223">[ 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/20110118/002224.html b/zarb-ml/mageia-dev/20110118/002224.html new file mode 100644 index 000000000..877420153 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002224.html @@ -0,0 +1,74 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mailing list for new RPMs + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mailing%20list%20for%20new%20RPMs&In-Reply-To=%3C20110118192826.GA4139%40shikamaru.fr%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002220.html"> + <LINK REL="Next" HREF="002316.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mailing list for new RPMs</H1> + <B>Remy CLOUARD</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mailing%20list%20for%20new%20RPMs&In-Reply-To=%3C20110118192826.GA4139%40shikamaru.fr%3E" + TITLE="[Mageia-dev] mailing list for new RPMs">shikamaru at mandriva.org + </A><BR> + <I>Tue Jan 18 20:28:26 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2224">[ date ]</a> + <a href="thread.html#2224">[ thread ]</a> + <a href="subject.html#2224">[ subject ]</a> + <a href="author.html#2224">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Tue, Jan 18, 2011 at 01:46:33PM +0000, Colin Guthrie wrote: +><i> 'Twas brillig, and Thierry Vignaud at 18/01/11 07:46 did gyre and gimble: +</I>><i> > Could we set up a mailing list for new uploaded RPMs like we had in Mandriva? +</I>><i> +</I>><i> ... and register it on GMane.org :) +</I>><i> +</I>I would be in favor of it too, with the ability to get a daily digest :) +-- +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/20110118/60302379/attachment.asc> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2224">[ date ]</a> + <a href="thread.html#2224">[ thread ]</a> + <a href="subject.html#2224">[ subject ]</a> + <a href="author.html#2224">[ 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/20110118/002225.html b/zarb-ml/mageia-dev/20110118/002225.html new file mode 100644 index 000000000..7788ea993 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002225.html @@ -0,0 +1,84 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Python Packaging Policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C20110118205126.31521fc6%40pitrou.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002223.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Python Packaging Policy</H1> + <B>Antoine Pitrou</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C20110118205126.31521fc6%40pitrou.net%3E" + TITLE="[Mageia-dev] Python Packaging Policy">solipsis at pitrou.net + </A><BR> + <I>Tue Jan 18 20:51:26 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2225">[ date ]</a> + <a href="thread.html#2225">[ thread ]</a> + <a href="subject.html#2225">[ subject ]</a> + <a href="author.html#2225">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Mon, 17 Jan 2011 09:21:56 +0100 +Michael scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +><i> +</I>><i> There is also the issue on bytecompilation ( <A HREF="https://qa.mandriva.com/show_bug.cgi?id=50484">https://qa.mandriva.com/show_bug.cgi?id=50484</A> ). +</I>><i> I have exposed there the various problem, and apart from explaining +</I>><i> that the solution I chosed was not better than the other, no one gave a compeling +</I>><i> argument into one or the others alternatives. +</I> +That depends how "compelling" you expect the argument to be :) +The current situation is clearly not satisfactory. +The solution of generating bytecode at install time looks fine. I am +not an RPM specialist though, but if you have non-RPM specific questions +feel free to ask them, I'd be glad to answer. + +><i> Finally, a vast part of the policy is handling 2to3, a topic that we didn't discuss +</I>><i> at all, and I would not be confortable to adopt it without first looking at it and +</I>><i> discussing it. +</I> +What is the issue with "handling 2to3"? It's a developer tool and +certainly shouldn't be invoked at install time if that's what you are +asking. Generally, I don't think you (as a packager) have to invoke +2to3 manually at all. If 2to3 is part of the packaged software's build +process, then their setup.py will probably invoke it automatically with +the right options. + +Regards + +Antoine. + + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2225">[ date ]</a> + <a href="thread.html#2225">[ thread ]</a> + <a href="subject.html#2225">[ subject ]</a> + <a href="author.html#2225">[ 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/20110118/002316.html b/zarb-ml/mageia-dev/20110118/002316.html new file mode 100644 index 000000000..079268319 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/002316.html @@ -0,0 +1,73 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GLUT%20%28part%20of%20mesa%20srpm%29%20is%20not%20GPL...%20and%20is%20quite%0A%09obsolete%20%21&In-Reply-To=%3C4D35A38E.9040806%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002224.html"> + <LINK REL="Next" HREF="002221.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete !</H1> + <B>Philippe DIDIER</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GLUT%20%28part%20of%20mesa%20srpm%29%20is%20not%20GPL...%20and%20is%20quite%0A%09obsolete%20%21&In-Reply-To=%3C4D35A38E.9040806%40laposte.net%3E" + TITLE="[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete !">philippedidier at laposte.net + </A><BR> + <I>Tue Jan 18 15:28:30 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2316">[ date ]</a> + <a href="thread.html#2316">[ thread ]</a> + <a href="subject.html#2316">[ subject ]</a> + <a href="author.html#2316">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi everybody ! + +I don't know if it's the right place to post this, and I don't want to +fill this mail list with long mesages... + +If someone needs to see what i'm talking about there's an old bug report +on Mandriva bugzilla that was recently resuscitated (I know Thierry +Vignaud had a glance on it...) +<A HREF="https://qa.mandriva.com/show_bug.cgi?id=47090">https://qa.mandriva.com/show_bug.cgi?id=47090</A> + +Perhaps it would be more sane and safe to start on a universal basis +with freeglut (that is used by every distribution), and build packages +with it (but that means a temporary problem of compatibility with +Mandriva...) + +Hope this will help + +philippe +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2316">[ date ]</a> + <a href="thread.html#2316">[ thread ]</a> + <a href="subject.html#2316">[ subject ]</a> + <a href="author.html#2316">[ 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/20110118/author.html b/zarb-ml/mageia-dev/20110118/author.html new file mode 100644 index 000000000..56d64cbd1 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/author.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 18 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>18 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>Tue Jan 18 00:06:25 CET 2011</i><br> + <b>Ending:</b> <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Messages:</b> 15<p> + <ul> + +<LI><A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2221"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2224"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A><A NAME="2316"> </A> +<I>Philippe DIDIER +</I> + +<LI><A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2220"> </A> +<I>Colin Guthrie +</I> + +<LI><A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2223"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="002212.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2212"> </A> +<I>Per Øyvind Karlsen +</I> + +<LI><A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2216"> </A> +<I>Motoko-chan +</I> + +<LI><A HREF="002225.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2225"> </A> +<I>Antoine Pitrou +</I> + +<LI><A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2213"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2214"> </A> +<I>Thomas Spuhler +</I> + +<LI><A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2215"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2222"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2218"> </A> +<I>Thierry Vignaud +</I> + +<LI><A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2219"> </A> +<I>andre999 +</I> + +<LI><A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2217"> </A> +<I>philippe makowski +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Archived on:</b> <i>Sun Jan 23 22:07:19 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/20110118/date.html b/zarb-ml/mageia-dev/20110118/date.html new file mode 100644 index 000000000..64ee7c3ef --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/date.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 18 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>18 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>Tue Jan 18 00:06:25 CET 2011</i><br> + <b>Ending:</b> <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Messages:</b> 15<p> + <ul> + +<LI><A HREF="002212.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2212"> </A> +<I>Per Øyvind Karlsen +</I> + +<LI><A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2213"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2214"> </A> +<I>Thomas Spuhler +</I> + +<LI><A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2215"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2216"> </A> +<I>Motoko-chan +</I> + +<LI><A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2217"> </A> +<I>philippe makowski +</I> + +<LI><A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2218"> </A> +<I>Thierry Vignaud +</I> + +<LI><A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2219"> </A> +<I>andre999 +</I> + +<LI><A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2220"> </A> +<I>Colin Guthrie +</I> + +<LI><A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A><A NAME="2316"> </A> +<I>Philippe DIDIER +</I> + +<LI><A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2221"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2222"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2223"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2224"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002225.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2225"> </A> +<I>Antoine Pitrou +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Archived on:</b> <i>Sun Jan 23 22:07:19 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/20110118/index.html b/zarb-ml/mageia-dev/20110118/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/index.html @@ -0,0 +1 @@ +thread.html
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/20110118/subject.html b/zarb-ml/mageia-dev/20110118/subject.html new file mode 100644 index 000000000..09c63b2b1 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/subject.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 18 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>18 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>Tue Jan 18 00:06:25 CET 2011</i><br> + <b>Ending:</b> <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Messages:</b> 15<p> + <ul> + +<LI><A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2214"> </A> +<I>Thomas Spuhler +</I> + +<LI><A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2215"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A><A NAME="2316"> </A> +<I>Philippe DIDIER +</I> + +<LI><A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2223"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2218"> </A> +<I>Thierry Vignaud +</I> + +<LI><A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2220"> </A> +<I>Colin Guthrie +</I> + +<LI><A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2224"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2221"> </A> +<I>Remy CLOUARD +</I> + +<LI><A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2222"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2216"> </A> +<I>Motoko-chan +</I> + +<LI><A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2219"> </A> +<I>andre999 +</I> + +<LI><A HREF="002212.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2212"> </A> +<I>Per Øyvind Karlsen +</I> + +<LI><A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2213"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2217"> </A> +<I>philippe makowski +</I> + +<LI><A HREF="002225.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2225"> </A> +<I>Antoine Pitrou +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Archived on:</b> <i>Sun Jan 23 22:07:19 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/20110118/thread.html b/zarb-ml/mageia-dev/20110118/thread.html new file mode 100644 index 000000000..560e07ff5 --- /dev/null +++ b/zarb-ml/mageia-dev/20110118/thread.html @@ -0,0 +1,149 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 18 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>18 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>Tue Jan 18 00:06:25 CET 2011</i><br> + <b>Ending:</b> <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Messages:</b> 15<p> + <ul> + +<!--0 01295305585- --> +<LI><A HREF="002212.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2212"> </A> +<I>Per Øyvind Karlsen +</I> + +<!--0 01295308449- --> +<LI><A HREF="002213.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2213"> </A> +<I>Michael Scherer +</I> + +<UL> +<!--1 01295308449-01295336343- --> +<LI><A HREF="002217.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2217"> </A> +<I>philippe makowski +</I> + +</UL> +<!--0 01295312852- --> +<LI><A HREF="002214.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2214"> </A> +<I>Thomas Spuhler +</I> + +<UL> +<!--1 01295312852-01295335459- --> +<LI><A HREF="002215.html">[Mageia-dev] Compatibility: %mdkversion macro? +</A><A NAME="2215"> </A> +<I>Maarten Vanraes +</I> + +</UL> +<!--0 01295335572- --> +<LI><A HREF="002216.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2216"> </A> +<I>Motoko-chan +</I> + +<UL> +<!--1 01295335572-01295339832- --> +<LI><A HREF="002219.html">[Mageia-dev] Proposal for Mageia: implement bitorrent protocol to allow updates download +</A><A NAME="2219"> </A> +<I>andre999 +</I> + +</UL> +<!--0 01295336774- --> +<LI><A HREF="002218.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2218"> </A> +<I>Thierry Vignaud +</I> + +<UL> +<!--1 01295336774-01295358393- --> +<LI><A HREF="002220.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2220"> </A> +<I>Colin Guthrie +</I> + +<UL> +<!--2 01295336774-01295358393-01295378906- --> +<LI><A HREF="002224.html">[Mageia-dev] mailing list for new RPMs +</A><A NAME="2224"> </A> +<I>Remy CLOUARD +</I> + +</UL> +</UL> +<!--0 01295360910- --> +<LI><A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete ! +</A><A NAME="2316"> </A> +<I>Philippe DIDIER +</I> + +<!--0 01295374020- --> +<LI><A HREF="002221.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2221"> </A> +<I>Remy CLOUARD +</I> + +<UL> +<!--1 01295374020-01295376484- --> +<LI><A HREF="002222.html">[Mageia-dev] Proofreading web applications policy +</A><A NAME="2222"> </A> +<I>Maarten Vanraes +</I> + +</UL> +<!--0 01295377172- --> +<LI><A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax +</A><A NAME="2223"> </A> +<I>Florian Hubold +</I> + +<!--0 01295380286- --> +<LI><A HREF="002225.html">[Mageia-dev] Python Packaging Policy +</A><A NAME="2225"> </A> +<I>Antoine Pitrou +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Jan 18 20:51:26 CET 2011</i><br> + <b>Archived on:</b> <i>Sun Jan 23 22:07:19 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> + |