diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101219/001807.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101219/001807.html | 134 |
1 files changed, 134 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101219/001807.html b/zarb-ml/mageia-dev/20101219/001807.html new file mode 100644 index 000000000..725da957f --- /dev/null +++ b/zarb-ml/mageia-dev/20101219/001807.html @@ -0,0 +1,134 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mageia sound tasks + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C4D0DDD61.8040104%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001806.html"> + <LINK REL="Next" HREF="001810.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mageia sound tasks</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C4D0DDD61.8040104%40laposte.net%3E" + TITLE="[Mageia-dev] mageia sound tasks">andr55 at laposte.net + </A><BR> + <I>Sun Dec 19 11:24:33 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001806.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001810.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1807">[ date ]</a> + <a href="thread.html#1807">[ thread ]</a> + <a href="subject.html#1807">[ subject ]</a> + <a href="author.html#1807">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael scherer a écrit : +><i> +</I>><i> On Sat, Dec 18, 2010 at 10:03:36AM +0100, SaschaS wrote: +</I>>><i> So I see basically that we need a guidline on how mageia deals with Spinoffs +</I>>><i> first. +</I> +It would probably be better to avoid spinoffs. The special interests - +sound in this case - would generally be followed by users that have +otherwise more or less average Mageia user interests. +In other words, they would generally want in other respects the standard +Mageia distro. +So instead of having a less well-maintained spinoff, wouldn't it be +better to have a few extra specialized packages in the contrib (or +equivalent) repositories of Mageia ? +I think so. + +<aside> +Of course there are those that want to eliminate a separate set of +contrib equivalent repos - but such a separation does seem useful, as in +this case.) +</aside> + +>><i> If all task are in the repos, I can understand those who say that there are +</I>>><i> to many task. +</I>><i> +</I>><i> The problem is not that there is too much more than the consequence of the +</I>><i> high number of task-*. +</I>><i> +</I>><i> rpmdrake, who is the main consumer of task-* rpm +</I>><i> convention, show all of them as 1 single list. So basically, with lots of tasks- +</I>><i> rpm, you just have a big unsorted list of category. Obviously not good for endusers. +</I>><i> +</I>><i> While it would be useful to group task into sound category, for the moment, +</I>><i> we cannot. +</I> +Why not ? +Unless of course there are plans to abandon Mandriva's rpm categories. +Using these rpm categories, of which sound is one, separation is handled +nicely. +Just try listing Mandriva meta/task packages, with rpm categories +active. I get 8 main categories, including sound. (A number of which +have subcategories.) +(I don't know if it is "meta" or "task" in English.) + +As well, if the folding proposals for mageia-app-db are carried to +rpmdrake (as I hope they will be), then task unfolding/expanding will +allow users to more easily see the real packages referenced by a task +package. +And hopefully allow selective installation of these referenced packages. +It seems that this will make the use of task packages more attractive. + +><i> One way would be to encode this information in the name ( ie, decide +</I>><i> that task-sound-foo and task-sound-bar are part of the sound category ). +</I> +No need to encode this into the name (unless one wants to). + +><i> I am not sure that using the name for this is a good idea. It is quite poor, +</I>><i> in term of metadata, and that's still a tree structure, while may a tag based +</I>><i> one may be better ( like Debian do, for example ). +</I>><i> +</I>><i> More ever, it doesn't make much sense to have task-lamp-* task-nagios and task-kde4 +</I>><i> at the same level, they are not destined at the same public. +</I> +Exactly why there are rpm categories. "Development" is not destined to +the same public as "Sound" or "Education". + +><i> Not to mention that installing rpm is ust half of the solution, configuration is +</I>><i> the other one. While we can to some extend push configuration in the rpm, there +</I>><i> is some that we cannot do reliably ( like adding a user to a group ). +</I>><i> +</I>><i> So maybe a wizard is a better solution than using a rpm that does magically everything. +</I> +Good point. Of course a task rpm could well install a configuration tool. + +my 2 cents :) + +André +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001806.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001810.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1807">[ date ]</a> + <a href="thread.html#1807">[ thread ]</a> + <a href="subject.html#1807">[ subject ]</a> + <a href="author.html#1807">[ 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> |