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-discuss/20101116/003017.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-discuss/20101116/003017.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101116/003017.html | 118 |
1 files changed, 118 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101116/003017.html b/zarb-ml/mageia-discuss/20101116/003017.html new file mode 100644 index 000000000..d1f404f6d --- /dev/null +++ b/zarb-ml/mageia-discuss/20101116/003017.html @@ -0,0 +1,118 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Introducing mageia-app-db + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Introducing%20mageia-app-db&In-Reply-To=%3C201011160009.58285.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="003018.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Introducing mageia-app-db</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Introducing%20mageia-app-db&In-Reply-To=%3C201011160009.58285.stormi%40laposte.net%3E" + TITLE="[Mageia-discuss] Introducing mageia-app-db">stormi at laposte.net + </A><BR> + <I>Tue Nov 16 00:09:58 CET 2010</I> + <P><UL> + + <LI>Next message: <A HREF="003018.html">[Mageia-discuss] Introducing mageia-app-db +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3017">[ date ]</a> + <a href="thread.html#3017">[ thread ]</a> + <a href="subject.html#3017">[ subject ]</a> + <a href="author.html#3017">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mardi 9 novembre 2010 05:57:36, andre999 a écrit : +><i> +</I>><i> Samuel Verschelde a écrit : +</I>><i> > +</I>><i> > Le vendredi 5 novembre 2010 06:38:14, andre999 a écrit : +</I>><i> > +</I>><i> >> As far as the question of application/package view goes, folding entries +</I>><i> >> (as in Rpmdrake groups or Nautilus) which expands to multi-line would be +</I>><i> >> nice. +</I>><i> >> That way complex packages like Openoffice or Firefox could be folded +</I>><i> >> into 2 or 3 lines. +</I>><i> >> (1 for localisation, another possibly for optional modules, another for +</I>><i> >> core modules.) +</I>><i> >> Now Firefox is more than 100 packages. +</I>><i> >> This sort of suggestion has been made for Rpmdrake. +</I>><i> >> The advantage of this approach is that the minimised view could be the +</I>><i> >> default, and at any time it can be expanded to show all packages, +</I>><i> >> without any configuration settings. +</I>><i> >> +</I>><i> > I'm not against, however how can we define those groups ? Is there a way to automate it ? Is it necessary to define it manually (and so to maintain it so have maintainers of these groups definitions) ? +</I>><i> > +</I>><i> First of all, the idea is to continue to use Mandriva-like categories +</I>><i> for the packages, as in Rpmdrake. So we associate packages within these +</I>><i> larger categories. +</I>><i> +</I>><i> The basic idea is to establish a hierarchy of views for multi-package +</I>><i> applications. +</I>><i> These associations should be designated according to guidelines, which +</I>><i> are yet to be established, according to the best judgement of the packager. +</I>><i> +</I>><i> Otherwise I don't see how we can arrive at consistant and useful +</I>><i> associations, especially if being used by different applications, like +</I>><i> Rpmdrake and your (very interesting and useful) project. It is +</I>><i> important that such applications are able to discern these associations, +</I>><i> in order to display them. +</I>><i> +</I>><i> First it will be useful to look at the different types of associations : +</I>><i> 1) Where usually all of the associated packages would be installed, such +</I>><i> as core packages of OpenOffice or Go-oo or LibreOffice. +</I>><i> +</I>><i> 2) Where usually only one - or a few - of the associated packages would +</I>><i> be installed, such as localisations. +</I>><i> +</I>><i> 3) Something in between, such as optional extensions for Firefox +</I>><i> +</I> +I read your whole post (had to come back 2 times to manage to finish it ! :)). + +Some comments : +- using a new tag to group packages together may be a solution for packages which have many optional subpackages, however this means we must reach a consensus among packagers. A complete proposal which have been tested on most of the examples you brought in your post could maybe help convincing other packagers. Adding a new tag is not a trivial move and maybe could break some compatibilty with other distributions, so I think it must be "proved" that it is the best solution (if it is). +- another simple way could be to group by source rpm. It won't always work, but that can be a first step, to experiment with. +- task meta-packages can be another solution +- we may have a look at what a package provides and group together packages whose names are close and which provide the same thing (eg. all packages which provide "openoffice.org-l10n" grouped together) +- it would be interesting to look at other distributions, to see how they solved or tried to solve this problem. How does ubuntu in its package manager for example ? + +If you have some free time and motivation, while we're waiting for the build system, you could maybe help us define how to show packages to users in mageia-app-db. If we can define a robust algorithm for package grouping, we'll try to implement it. + +Another problem you mentioned is how to define what an "application" is. We could use some help on this subject too :) + +You can have a look at this wiki page (on our new Redmine project, thanks to Jehane for setting it up) which is dedicated to this matter : <A HREF="http://mageia-app-db.tuxette.fr/projects/mageia-app-db/wiki/Applications">http://mageia-app-db.tuxette.fr/projects/mageia-app-db/wiki/Applications</A> + +Regards + +Samuel Verschelde +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="003018.html">[Mageia-discuss] Introducing mageia-app-db +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3017">[ date ]</a> + <a href="thread.html#3017">[ thread ]</a> + <a href="subject.html#3017">[ subject ]</a> + <a href="author.html#3017">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |