From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dilfridge@gentoo.org
Subject: Re: [gentoo-dev] repoman feature request / profiles.desc profile types
Date: Mon, 17 Feb 2014 18:52:21 +0100 [thread overview]
Message-ID: <20140217185221.49af7d39@gentoo.org> (raw)
In-Reply-To: <201402161758.43311.dilfridge@gentoo.org>
On Sun, 16 Feb 2014 17:58:39 +0100
"Andreas K. Huettel" <dilfridge@gentoo.org> wrote:
>
> Hi all,
>
> Right now we have arches maintaining a stable keyword and we have
> arches that don't do that.
>
> This makes me think that the classification of profiles as "exp",
> "dev", "stable" in profiles.desc does not really cover all usecases.
>
> [Current meaning:
> "stable" - repoman checks it, arch has stable keyword
> "dev" - repoman checks it with -d
> "exp" - repoman ignores it]
>
> I'd like to propose two additional profile types:
> "nonstable" - repoman checks it, arch has no stable keyword (and if
> there is one in an ebuild, repoman treats it as arch=~arch)
> "dev-nonstable" - repoman checks it with -d, arch has no stable
> keyword (and if there is one in an ebuild, repoman treats it as
> arch=~arch)
+1
(dev-nonstable isnt really appealing as history has proved that nobody
dares to check deptree for dev/exp profiles)
> Why not make it possible to keep an ~arch only deptree consistent?!
it is possible, there's just a lot of confusion around it :)
this "cosmetic" change should really help in avoiding this confusion
Alexis.
prev parent reply other threads:[~2014-02-17 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 16:58 [gentoo-dev] repoman feature request / profiles.desc profile types Andreas K. Huettel
2014-02-16 17:18 ` [gentoo-dev] " Michael Palimaka
2014-02-16 18:36 ` Andreas K. Huettel
2014-02-16 19:29 ` Michael Palimaka
2014-02-17 17:52 ` Alexis Ballier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140217185221.49af7d39@gentoo.org \
--to=aballier@gentoo.org \
--cc=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox