Gentoo Archives: gentoo-dev

From: Mike Frysinger <vapier@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy
Date: Wed, 22 Jan 2014 06:58:15
In Reply to: Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy by William Hubbs
1 On Monday 20 January 2014 12:26:13 William Hubbs wrote:
2 > On Mon, Jan 20, 2014 at 02:23:24AM -0500, Mike Frysinger wrote:
3 > > this has all been fairly ad-hoc in the past, so formalize it in the one
4 > > place that impacts everyone -- profiles.desc.
5 >
6 > If it is policy, shouldn't it go in the dev manual rather than in this
7 > file?
9 maybe. devmanual doesn't talk about this file at all atm.
11 or maybe i still have it in my head that devmanual.g.o is the ad-hoc
12 documentation and not a policy manual -- policy lives in the Gentoo Developer
13 Handbook.
15 > There are several situations in profiles.desk where one profile is dev
16 > but some profiles that inherit it are exp, for example, the arm
17 > profiles.
18 >
19 > Which rule applies in this scenario?
21 both. when you run `repoman`, it isn't just checking for $ARCH and ~$ARCH
22 consistency. it is doing that for every single profile (one of the reasons
23 repoman is slow -- every time we add a profile, that's another dependency tree
24 repoman needs to check). when people say "the dependency tree for $ARCH is
25 broken", there's a qualifier in there that people rarely include. the dep tree
26 *for a specific profile* is broken. usually breakage covers them all, but since
27 things like use.mask and package.use.mask and package.mask are done on a per-
28 profile basis, it's not that uncommon for the breakage to hit a subset of
29 profiles.
31 that means package maintainers are allowed to break exp profiles. they should
32 avoid breaking dev profiles, but they can fall back to filing bugs for the
33 profile maintainers (which usually means the $ARCH maintainer).
35 the quick rule of thumb in terms of "what do package maintainers need to care
36 about for $ARCH", then look at it in terms of "what is the best profile
37 available for $ARCH".
39 > Also, from a maintainer's pov, what is the difference between stable and
40 > dev profiles?
42 for package maintainers, you get smacked if you break "stable" profiles because
43 that's what the majority of users have selected. if you break a "dev" profile,
44 that's not a huge deal as people know things are "in progress".
45 -mike


File name MIME type
signature.asc application/pgp-signature