diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/010980.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-January/010980.html | 147 |
1 files changed, 147 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/010980.html b/zarb-ml/mageia-dev/2012-January/010980.html new file mode 100644 index 000000000..cacf1f2bd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/010980.html @@ -0,0 +1,147 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20task-obsolete%20and%20README.%2A.urpmi%20enhancement&In-Reply-To=%3C4F059D72.5030303%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010958.html"> + <LINK REL="Next" HREF="010985.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement</H1> + <B>Guillaume Rousse</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20task-obsolete%20and%20README.%2A.urpmi%20enhancement&In-Reply-To=%3C4F059D72.5030303%40gmail.com%3E" + TITLE="[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement">guillomovitch at gmail.com + </A><BR> + <I>Thu Jan 5 13:54:10 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="010958.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement +</A></li> + <LI>Next message: <A HREF="010985.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10980">[ date ]</a> + <a href="thread.html#10980">[ thread ]</a> + <a href="subject.html#10980">[ subject ]</a> + <a href="author.html#10980">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 04/01/2012 20:13, Luc Menut a écrit : +><i> Le 04/01/2012 17:20, Guillaume Rousse a écrit : +</I>>>><i> 1) add support for optional README.*.urpmi (%ghost in spec): +</I>>>><i> This will allow to build this README.*.urpmi at install time in %pre, +</I>>>><i> %post or %trigger only when it's necessary. +</I>>><i> That will create files on the system unknown from rpm database, and +</I>>><i> unknown from urpmi too. +</I>><i> +</I>><i> nope, %ghost files are known from rpm database. +</I>><i> rpm -qpl task-obsolete-1-1.mga2.noarch.rpm +</I>><i> /usr/share/doc/task-obsolete +</I>><i> /usr/share/doc/task-obsolete/README.null-dummy.obsolete.urpmi +</I>><i> /usr/share/doc/task-obsolete/README.null.obsolete.urpmi +</I>Then the database will always contains entries for some files that only +will potentially exist on the systeme. The whole idea of conditionnaly +creating files in post-installation seems a bad idea. + +>><i> Rather than focusing on shiny automatic display mechanisms, I'd rather +</I>>><i> work on information content. +</I>><i> +</I>><i> we can|should do both. +</I>><i> +</I>><i> [...] +</I>>><i> +</I>>><i> Here are a few proposal of mines to make the situation better: +</I>>><i> - use a unique file name, enforced by convention, rather than references +</I>>><i> in package description, the same way Debian does with README.debian +</I>>><i> - display its content only in graphical context: command-line users +</I>>><i> usually know about this kind of convention to get information themselves +</I>>><i> - use standardised file content and markup to allow rpmdrake and other +</I>>><i> graphical tools to achieve the same kind of selection than file +</I>>><i> splitting today +</I>>><i> - define some kind of policy of what should be there, and what should +</I>>><i> not, to achieve minimal consistency +</I>><i> +</I>><i> I'm not particularly attached at the current system, but I find it works +</I>><i> rather well. +</I>><i> If we want that users read informations, the information should be +</I>><i> relevant in the context (too many informations, kill information); +</I>Indeed, that's why I suggest using standardised documentation templates +and conventions, rather than automated mecanisms. + +><i> e.g. it's useless (personnaly, I consider it's bad) to display +</I>><i> information about install when we update a package, and vice versa (I +</I>><i> don't know debian, and if the unique file README.debian allow this). +</I>The README.debian is just a plain old reference text file, and is never +automatically displayed. Debian does however has a powerful +post-installation interactive mecanism (debconf), which is usually used +for configuration, but could also get used for this kind of +context-specific information. + +I completly agree on the generic idea of making information access +easier. But I wouldn't reduce this to just extracting the minimal subset +of relevant information so as to display it automatically. Especially if +the suggested implementation involves messing with rpm idea of installed +files, and also make information access more complex for users as myself +who prefer to read plain old documentation files manually. + +This kind of context-dependant logic should better get implemented in +the installer rather than individual packages. And even in that case, +the added value of a technical solution someone will have to maintain +over a simple remark in flashplayer plugin package documentation is +discussable. +-- +BOFH excuse #62: + +need to wrap system in aluminum foil to fix problem +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010958.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement +</A></li> + <LI>Next message: <A HREF="010985.html">[Mageia-dev] RFC: task-obsolete and README.*.urpmi enhancement +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10980">[ date ]</a> + <a href="thread.html#10980">[ thread ]</a> + <a href="subject.html#10980">[ subject ]</a> + <a href="author.html#10980">[ 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> |