Gentoo Archives: gentoo-dev

From: "Robin H. Johnson" <robbat2@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Proposal: pre-emerge advisories
Date: Thu, 14 Jul 2005 07:38:51
Message-Id: 20050714073615.GA1429@curie-int.orbis-terrarum.net
In Reply to: Re: [gentoo-dev] Proposal: pre-emerge advisories by "Kevin F. Quinn"
1 On Thu, Jul 14, 2005 at 09:17:38AM +0200, Kevin F. Quinn wrote:
2 > On 14/7/2005 7:24:03, Craig Lawson (craig.lawson@××××××××.edu) wrote:
3 > > [...] To be more concrete, I'm thinking of something like a database [...]
4 > I don't think a separate database is a good idea; too many sources for information.
5 How about using metadata.xml? I'd think this data is ideally suited for
6 it. It's metadata about the package, and it's already distributed with
7 the tree.
8
9 > > [...] For example [...]
10 > > current: any
11 > > target: =gnome-base/gnome-menus-2.10.0
12 > > advisory: Menu editing disabled until follow-up release.
13 > > Work-around is to install Python 4 + smeg. See
14 > > forum topic http://forums.gentoo.org/blah...
15 >
16 > How about adding:
17 >
18 > ADVICE="Menu editing disabled until follow-up release.
19 > Work-around is to install Python 4 + smeg. See
20 > forum topic http://forums.gentoo.org/blah..."
21 >
22 > to the gnome-menus-2.10.0 ebuild (sorry Chris, no parsing needed :} ).
23 > It'd be trivial to knock up a widget to extract and display this data,
24 > and I'd guess trivial to add an '--advice' option to emerge to do the
25 > same. Perhaps it'd be simpler just to include it alongside the
26 > changelog data with the '--changelog' option.
27 Putting it in the ebuild becomes a bit complex when you want to include
28 lots of text, or if you want to display a message for a specific
29 downgrade or something else like that. Basically while you have the
30 'target' attribute, you have no way to specify the 'current' attribute,
31 and you can't have multiple advisories per ebuild.
32
33 metadata.xml variant:
34 <pkgmetadata><advisory target="=gnome-base/gnome-menus-2.10.0">
35 Menu editing disabled until follow-up release.
36 Work-around is to install Python 4 + smeg. See
37 forum topic http://forums.gentoo.org/blah...
38 </advisory></pkgmetadata>
39 ('current' attribute defaulting to any version, and both the 'target'
40 and 'current' attributes should be full package atoms.)
41
42 > Of course such advice could be just written into the changelog in the first place...
43 The problem is that users complain and don't read the changelog, since
44 it's too long. They want only specific advisories that are needed, not
45 every little change notice.
46
47 --
48 Robin Hugh Johnson
49 E-Mail : robbat2@××××××××××××××.net
50 Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
51 ICQ# : 30269588 or 41961639
52 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85

Replies

Subject Author
Re: [gentoo-dev] Proposal: pre-emerge advisories Georgi Georgiev <chutz@×××.net>