1 |
On Mon, 21 Mar 2005 06:11:28 +0100 |
2 |
Marius Mauch <genone@g.o> wrote: |
3 |
|
4 |
> (no tool support for either solution) |
5 |
|
6 |
Well, actually i've put some bits of code in the bugreport I've |
7 |
mentioned above, so there is tool support for the use.local.desc |
8 |
solution (equery and emerge). That was more to demonstrate how |
9 |
easy it was to implement tho, and i agree it's not the only point |
10 |
of the discussion. |
11 |
|
12 |
> use.local.desc for package-specific short descriptions (like at |
13 |
> the moment) and metadata.xml for longer detailed descriptions |
14 |
> if required |
15 |
|
16 |
That sounds like a good idea. So, to summarize (just to check |
17 |
i've understood your proposal): |
18 |
|
19 |
- users should know when a flag is really a must-have for a |
20 |
given package, or is at the contrary not advised, things like |
21 |
that. That kind of quick hints, warnings, and other answers to |
22 |
obvious questions like "Is DVD support by mplayer better with the |
23 |
'dvdread' flag?" only require short notes (one sentence) in |
24 |
general. But what is important is that they get written whenever |
25 |
there is something to say about a flag which is not already in |
26 |
use.desc (because package-specific), and that they are easily |
27 |
accessible for the user. Here, use.local.desc seems better, |
28 |
because there is no such thing as an "echo >>" to drop a quick |
29 |
note somewhere, and because it doesn't require complex code or |
30 |
access to multiple files to get optionaly displayed by emerge in |
31 |
pretend mode. |
32 |
|
33 |
- user might sometimes wonder what is the "libfoo" that the "foo" |
34 |
flag description ("add support for libfoo") talks about. That may |
35 |
require a long description (one paragraphe), which don't need to |
36 |
be in use.local.desc. Metadata.xml is fine here, since anyway |
37 |
that's the kind of things you write using a text editor. |
38 |
|
39 |
That raises on more question tho: if someone wants to write a |
40 |
long description for a global flag, where does he do it? |
41 |
|
42 |
-- |
43 |
TGL. |
44 |
-- |
45 |
gentoo-dev@g.o mailing list |