diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101026/002668.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101026/002668.html | 150 |
1 files changed, 150 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101026/002668.html b/zarb-ml/mageia-discuss/20101026/002668.html new file mode 100644 index 000000000..9730611b5 --- /dev/null +++ b/zarb-ml/mageia-discuss/20101026/002668.html @@ -0,0 +1,150 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Suggestions + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C4CC6A6B2.6090105%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002667.html"> + <LINK REL="Next" HREF="002665.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Suggestions</H1> + <B>andre999</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C4CC6A6B2.6090105%40laposte.net%3E" + TITLE="[Mageia-discuss] Suggestions">andr55 at laposte.net + </A><BR> + <I>Tue Oct 26 12:00:18 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002667.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002665.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2668">[ date ]</a> + <a href="thread.html#2668">[ thread ]</a> + <a href="subject.html#2668">[ subject ]</a> + <a href="author.html#2668">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Kira a écrit : +><i> +</I>><i> 在 Tue, 26 Oct 2010 13:22:52 +0800, andre999 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">andr55 at laposte.net</A>>寫道: +</I>><i> +</I>>><i> I don't quite follow this distinction of programs and packages. +</I>>><i> A package is a file with installation instructions for a program, or +</I>>><i> a set of closely related programs. Sometimes a program with many +</I>>><i> modules is divided into more than one package, but then there are one +</I>>><i> or more core packages, essential to the installation of the others. +</I>>><i> So maybe some packages would need minimal documentation since they +</I>>><i> are dependant on a core package (e.g. OpenOffice). +</I>>><i> But if considering installing a package containing a number of +</I>>><i> closely related programs, wouldn't one want all the contained +</I>>><i> programs to be documented ? +</I>>><i> Since they would almost necessarily be complementary ? +</I>>><i> And if you install only one program at a time, essentially you are +</I>>><i> saying that each package contains exactly one program. So you want +</I>>><i> 37 packages to install Openoffice ? And you want 4 or 5 packages +</I>>><i> instead of one for the diff (file comparison) utilities ? +</I>><i> The difference is clear: For most of the time, you would install +</I>><i> programs, +</I>><i> not packages. Currently in the RPMDRAKE, libraries are listed, +</I>><i> localizations +</I>><i> are listed, which is annoying since if you are not programmer, why +</I>><i> would you +</I>><i> cares about these things? Sure, some would need them for their own +</I>><i> purpose, +</I>><i> but most of the time we would only focus on install certain program, not +</I>><i> related libraries/localizations/....etc. They should go into expert mode/ +</I>><i> detail mode, not directly exposed to people. This is a usability +</I>><i> problem, not +</I>><i> about packaging. +</I>It is essential to be able to readily select localisations, for those +needing something other than English. +><i> +</I>>><i> By the way, if newbies are scared off by packages, why is the +</I>>><i> Microsoft environment package oriented ? +</I>>><i> (Even though often a package of numerous programs is referred to as a +</I>>><i> program.) +</I>>><i> +</I>><i> I think you miss-understand my thought. That's something like task +</I>><i> package, +</I>><i> which is not what I was talking about. I meant the packages like +</I>><i> libktorrent, +</I>><i> which is installed together with ktorrent as the backbone library. +</I>><i> It's listed +</I>><i> in RPMDRAKE, but in what normal condition would you install it solely? +</I>><i> NO. You install KTorrent, not libktorrent. It should be hidden by +</I>><i> RPMDRAKE, +</I>><i> unless you check the option to show all packages. Most of the time, +</I>><i> you won't +</I>><i> care about what packages installed on your system, you cares about what +</I>><i> "softwares" are installed. +</I> +OK, I understand now. You want to show only ordinary program packages, +and not libraries or localisations. +But libraries are in their own section, if you list packages by category. +And localisations are useful packages to show, unless you want to +install them all. +Or you have another way to ensure that only wanted localisations are +installed. +That could be useful. + +This reminds me of a suggestion I made a while back for rpmdrake -- that +packages can be grouped multi-level, such that related packages, such as +localisations or modules of a package, be folded to a single line (or +expanded to multiple lines), to greatly reduce the number of lines +displayed. +(e.g. Openoffice or Firefox.) +To accommodate this, Rpmdrake would have to be modified to have multiple +(2 or 3) selection columns. One could select multiple packages with one +click, if folded into one line, or expand the line to select only one or +a few of the packages inside. +A good example would be Openoffice, could now be displayed by default in +only 3 lines : the base package, the various modules (Writer, Calc, +Draw, etc), and the localisations. One could select the base and +modules in 2 clicks, and open the localisations to select the +language(s) desired. Instead of seeing approximately 100 lines. +(I just counted, probably miscounting a bit. In fact it was about 300, +as there were the release and 2 updates for each package.) +Note that many related libraries are divided into a number of modules as +well, so the same principle could apply there. + +Anyway, however we do it, there is definitely room for improvement in +Rpmdrake. :) + +- André + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002667.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002665.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2668">[ date ]</a> + <a href="thread.html#2668">[ thread ]</a> + <a href="subject.html#2668">[ subject ]</a> + <a href="author.html#2668">[ 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> |