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/2011-October/008869.html | |
parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/008869.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-October/008869.html | 207 |
1 files changed, 207 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/008869.html b/zarb-ml/mageia-dev/2011-October/008869.html new file mode 100644 index 000000000..02e5b8a4d --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/008869.html @@ -0,0 +1,207 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] RPM features/issues/wishlist + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RPM%20features/issues/wishlist&In-Reply-To=%3CCAPn0va5JnxjhXi2C0kDZsxbjKv%2BdTtW7R1Nm%2BDPGqtyVig4VVA%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="008868.html"> + <LINK REL="Next" HREF="008871.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] RPM features/issues/wishlist</H1> + <B>Donald Stewart</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RPM%20features/issues/wishlist&In-Reply-To=%3CCAPn0va5JnxjhXi2C0kDZsxbjKv%2BdTtW7R1Nm%2BDPGqtyVig4VVA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] RPM features/issues/wishlist">watersnowrock at gmail.com + </A><BR> + <I>Sat Oct 15 01:32:41 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="008868.html">[Mageia-dev] RPM features/issues/wishlist +</A></li> + <LI>Next message: <A HREF="008871.html">[Mageia-dev] RPM features/issues/wishlist +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8869">[ date ]</a> + <a href="thread.html#8869">[ thread ]</a> + <a href="subject.html#8869">[ subject ]</a> + <a href="author.html#8869">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 14 October 2011 16:13, Per Øyvind Karlsen <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">peroyvind at mandriva.org</A>> wrote: +><i> 2011/10/14 Donald Stewart <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">watersnowrock at gmail.com</A>>: +</I>>><i> On 14 October 2011 11:36, Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> wrote: +</I>>>><i> Le vendredi 14 octobre 2011 20:33:29, Per Øyvind Karlsen a écrit : +</I>>>>><i> 2011/10/14 Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>>: +</I>>>>><i> > Le vendredi 14 octobre 2011 19:30:01, Samuel Verschelde a écrit : +</I>>>>><i> >> Le vendredi 14 octobre 2011 16:19:18, Per Øyvind Karlsen a écrit : +</I>>>>><i> >> > I've started to ramble on some of the features, issues, ideas etc. to +</I>>>>><i> >> > work on and consider +</I>>>>><i> >> > for our (Mandriva Linux) next development cycle, and in the interest +</I>>>>><i> >> > of sharing work and +</I>>>>><i> >> > coordinating efforts with others, while inviting others to contribute: +</I>>>>><i> >> > <A HREF="http://wiki.mandriva.com/en/Development/Tasks/Packaging/Tools/RPM/TODO">http://wiki.mandriva.com/en/Development/Tasks/Packaging/Tools/RPM/TODO</A> +</I>>>>><i> >> > +</I>>>>><i> >> > While it's certainly written from a vendor POV (and also rather crude +</I>>>>><i> >> > for the moment), I'm cross-posting +</I>>>>><i> >> > this one as it's of potential interest to others as well and the idea +</I>>>>><i> >> > is for things to be as generic as +</I>>>>><i> >> > possible anyhows.. :) +</I>>>>><i> >> > +</I>>>>><i> >> > So I invite others with the interest to contribute to the discussion +</I>>>>><i> >> > on the list and wiki, proposing +</I>>>>><i> >> > ideas, gather a list of issues that needs to be addressed, and do some +</I>>>>><i> >> > general brainstorming +</I>>>>><i> >> > and uhm.. "stuff". ;) +</I>>>>><i> >> +</I>>>>><i> >> I don't know RPM internals well, the only thing that comes to my mind is +</I>>>>><i> >> improved packagekit support for Mandriva / Mageia. +</I>>>>><i> +</I>>>>><i> Don't necessarily need to know RPM internals for proposing features, +</I>>>>><i> or issues you'd +</I>>>>><i> like to see be solved. :) +</I>>>>><i> +</I>>>>><i> > Maybe also the package management related items in the Mageia 2 specs can +</I>>>>><i> > be of interest: +</I>>>>><i> > <A HREF="http://mageia.org/wiki/doku.php?id=iso2:technical_specification#package_m">http://mageia.org/wiki/doku.php?id=iso2:technical_specification#package_m</A> +</I>>>>><i> > anagement_infrastructure +</I>>>>><i> +</I>>>>><i> Ah, yes, most certainly. :) +</I>>>>><i> +</I>>>>><i> I can leave some comments on your wiki, while adding what I personally +</I>>>>><i> find useful and interesting to my +</I>>>>><i> wiki page where I'll keep track of it's current progress (at my end at +</I>>>>><i> least;). +</I>>>><i> +</I>>>><i> Please note that this wiki page is readonly (don't trust the wiki if it lets +</I>>>><i> you edit it). The place for discussion is bugzilla (each item should have an +</I>>>><i> entry in bugzilla, even if it's not the case currently). +</I>>>><i> +</I>>>><i> Best regards +</I>>>><i> +</I>>>><i> Samuel +</I>>>><i> +</I>>><i> +</I>>><i> Improving packagekit would be great, not having a qt based package +</I>>><i> manager is annoying. +</I>><i> Yupp, you'll find several new features the urpmi backend was lacking +</I>><i> implemented in my branch. +</I>><i> Keep in mind though that packagekit is designed in a very generic way, +</I>><i> with the features that packagekit lacks, it's not as simple as just going +</I>><i> ahead and implement it in the backend, support also needs to be +</I>><i> implemented in the frontend as well. +</I>><i> And if you want some new feature making it into packagekit upstream, +</I>><i> you need to have some consencus on it and take other distros into +</I>><i> consideration as well, so there might potentially be features of rpmdrake +</I>><i> that will be hard, if ever to get properly implemented in packagekit +</I>><i> and maintained upstream.. +</I>><i> +</I>><i> In the scenario for how I'd like to see packagekit adopted for Mandriva and MPM +</I>><i> for instance, I'm kinda expecting having to go ahead and just +</I>><i> implement and maintain +</I>><i> some features in our own backend only that might not be part of +</I>><i> packagekit's features +</I>><i> or supported by other frontends for it etc. (at least not immediately). +</I>><i> +</I>><i> Well, that's just some thoughts I've had on the potential challenges +</I>><i> of packagekit +</I>><i> and to warn against having too high expectations towards packagekit +</I>><i> frontends replacing +</I>><i> existing ones.. :) +</I>><i> +</I>><i> Is there any particular features in the packagekit feature matrix +</I>><i> you're missing btw.? +</I>><i> ('what-provides' has already been implemented in my branch </FYI>:) +</I>>><i> +</I>>><i> The only other thing that I would like to see, although i think it is +</I>>><i> more or a urpm issue than rpm is adding parallel downloads, so that +</I>>><i> when packages are being installed, it keeps on downloading the next +</I>>><i> set to be installed. +</I>><i> Yupp, already on urpmi's suggested feature list since a while ago, +</I>><i> although it would have +</I>><i> to be implemented at a much higher level in urpmi perl code by adding +</I>><i> separate threads +</I>><i> downloading and package installation.. I'm a wuzz at perl and awaiting +</I>><i> for a new perl +</I>><i> maintainer to arrive to hand of such very perly details to implement, +</I>><i> so it's on the list, +</I>><i> but likely not to be done (in urpmi) by me. :) +</I>><i> +</I>><i> -- +</I>><i> Regards, +</I>><i> Per Øyvind +</I>><i> +</I> +The thing about packagekit, well most graphical frontends package +management (pm) is that they dont really need to be that functional. +By that I mean that yes it is great to be able to query nearly all of +urpmi's features in rpmdrake, however, isn't it much faster to just do +urpmf --files file-name. I guess what I am getting at is that as long +as basic functionality, eg searching, add/remove and repo +configurations are handled by the pm and done properly, ie not causing +any breakage, then I feel that it is fair enough to say that more +advanced functions should be done on the cl, firstly because that way +is easier, secondly because that way encourages less breakage from +just point and click and see. +One feature of rpmdrake that i do really like is that you can +configure it to search by {name,description.......} this helps a lot +for finding software that you don't know the specifics for before +hand, and the only real case where a gui frontend comes into its own +for pm so I guess that as long as that is supported, with being able +to see arch, and release numbers, I am happy to have a basic pm +system. + +I remember seeing that list somewhere, hence why i wasn't sure. Well, +I am about as good at speaking pearl as i am at finding perl's so i +guess that counts me out :) +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008868.html">[Mageia-dev] RPM features/issues/wishlist +</A></li> + <LI>Next message: <A HREF="008871.html">[Mageia-dev] RPM features/issues/wishlist +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8869">[ date ]</a> + <a href="thread.html#8869">[ thread ]</a> + <a href="subject.html#8869">[ subject ]</a> + <a href="author.html#8869">[ 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> |