diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101218/001791.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101218/001791.html | 89 |
1 files changed, 89 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101218/001791.html b/zarb-ml/mageia-dev/20101218/001791.html new file mode 100644 index 000000000..2b22ed491 --- /dev/null +++ b/zarb-ml/mageia-dev/20101218/001791.html @@ -0,0 +1,89 @@ +<!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=%3C20101218153450.GB18333%40sisay.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001781.html"> + <LINK REL="Next" HREF="001792.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mageia sound tasks</H1> + <B>Michael scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C20101218153450.GB18333%40sisay.ephaone.org%3E" + TITLE="[Mageia-dev] mageia sound tasks">misc at zarb.org + </A><BR> + <I>Sat Dec 18 16:34:50 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001781.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001792.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1791">[ date ]</a> + <a href="thread.html#1791">[ thread ]</a> + <a href="subject.html#1791">[ subject ]</a> + <a href="author.html#1791">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Dec 18, 2010 at 10:03:36AM +0100, SaschaS wrote: +><i> So I see basically that we need a guidline on how mageia deals with Spinoffs +</I>><i> first. +</I>><i> +</I>><i> If all task are in the repos, I can understand those who say that there are +</I>><i> to many task. +</I> +The problem is not that there is too much more than the consequence of the +high number of task-*. + +rpmdrake, who is the main consumer of task-* rpm +convention, show all of them as 1 single list. So basically, with lots of tasks- +rpm, you just have a big unsorted list of category. Obviously not good for endusers. + +While it would be useful to group task into sound category, for the moment, +we cannot. One way would be to encode this information in the name ( ie, decide +that task-sound-foo and task-sound-bar are part of the sound category ). + +I am not sure that using the name for this is a good idea. It is quite poor, +in term of metadata, and that's still a tree structure, while may a tag based +one may be better ( like Debian do, for example ). + +More ever, it doesn't make much sense to have task-lamp-* task-nagios and task-kde4 +at the same level, they are not destined at the same public. + +Not to mention that installing rpm is ust half of the solution, configuration is +the other one. While we can to some extend push configuration in the rpm, there +is some that we cannot do reliably ( like adding a user to a group ). + +So maybe a wizard is a better solution than using a rpm that does magically everything. + +-- +Michael Scherer +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001781.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001792.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1791">[ date ]</a> + <a href="thread.html#1791">[ thread ]</a> + <a href="subject.html#1791">[ subject ]</a> + <a href="author.html#1791">[ 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> |