diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110202/002417.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110202/002417.html | 113 |
1 files changed, 113 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110202/002417.html b/zarb-ml/mageia-dev/20110202/002417.html new file mode 100644 index 000000000..9defb2630 --- /dev/null +++ b/zarb-ml/mageia-dev/20110202/002417.html @@ -0,0 +1,113 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] announcing magpie + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20announcing%20magpie&In-Reply-To=%3C20110202170005.GI6023%40mongueurs.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002415.html"> + <LINK REL="Next" HREF="002416.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] announcing magpie</H1> + <B>Jerome Quelin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20announcing%20magpie&In-Reply-To=%3C20110202170005.GI6023%40mongueurs.net%3E" + TITLE="[Mageia-dev] announcing magpie">jquelin at gmail.com + </A><BR> + <I>Wed Feb 2 18:00:05 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002415.html">[Mageia-dev] announcing magpie +</A></li> + <LI>Next message: <A HREF="002416.html">[Mageia-dev] Packager meetings for tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2417">[ date ]</a> + <a href="thread.html#2417">[ thread ]</a> + <a href="subject.html#2417">[ subject ]</a> + <a href="author.html#2417">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 11/02/02 16:33 +0100, nicolas vigier wrote: +><i> > Hm, for such seemingly trivial feature additions, wouldn't it make more sense +</I>><i> > to just implement it in repsys..? +</I>><i> +</I>><i> Jerome makes his scripts in perl. And mgarepo is in python. So it makes +</I>><i> sense to distribute it separatly. And some of the features can still be +</I>><i> implemented later in mgarepo if it appears they are useful to a lot of +</I>><i> people ... +</I> +more importantly, those trivial features are designed to be coupled +later on. and this will be much easier to do if every action is +available in a module of its own... + +eg, here are some other scripts that i have, intend to clean & port to +magpie subcommands: + + - update a perl module to latest version without having to specify said + version. i already have sthg that works (for more than 2 years), + which means that to update a pkg in mandriva i used to do: + $ cooker perl-Foo-Bar && refresh + ("cooker" command was the equivalent of "magpie co") + + - list all perl modules needing to be updated, grouped by core, + dual-lifed or regular modules. i used to do the following to know + which modules to update: + $ cpan-old + + - order a group of packages to be rebuilt according to their build + requires. this allowed me to rebuild ~2400 perl packages for mageia + quite easily. + +now, the grand plan for magpie is to integrate all those commands & then +to create a new subcommand that would automatically: + - run cpan-old (magpie xxx to be created) + - sort them according to their buildrequires (magpie xxx to be + created) + - for each of them, check it out (magpie co) + - get latest version, update, build & submit (magpie xxx to be + created) + - wait a bit if needed (magpie bswait) + - go back to step 2 + +now, you do understand that even if perl allows me to seemlessly call +various scripts written in whatever language (bash, python, etc), having +all subcommands sanitized and available as module will make all the +plumbing much more efficient, clean & maintainable. + +oh - another thing. had i decided not to clean my collection of scripts +and publish them as a perl module, those scripts would still sit on my +computer and would not be shared. and i definitely think that it's a +good thing to share: it will allow people to help maintain perl packages +(and thus reducing my workload), not counting the fact that it may be +useful for other distributions too (*cough* mandriva *cough*). + +hoping to clarify the rationale of magpie, +jérôme +-- +<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">jquelin at gmail.com</A> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002415.html">[Mageia-dev] announcing magpie +</A></li> + <LI>Next message: <A HREF="002416.html">[Mageia-dev] Packager meetings for tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2417">[ date ]</a> + <a href="thread.html#2417">[ thread ]</a> + <a href="subject.html#2417">[ subject ]</a> + <a href="author.html#2417">[ 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> |