public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] repoman feature request / profiles.desc profile types
Date: Sun, 16 Feb 2014 17:58:39 +0100	[thread overview]
Message-ID: <201402161758.43311.dilfridge@gentoo.org> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 925 bytes --]


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)

Why not make it possible to keep an ~arch only deptree consistent?!

Cheers, 
Andreas

-- 
Andreas K. Huettel
Gentoo Linux developer (council, kde)
dilfridge@gentoo.org
http://www.akhuettel.de/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2014-02-16 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16 16:58 Andreas K. Huettel [this message]
2014-02-16 17:18 ` [gentoo-dev] Re: repoman feature request / profiles.desc profile types Michael Palimaka
2014-02-16 18:36   ` Andreas K. Huettel
2014-02-16 19:29     ` Michael Palimaka
2014-02-17 17:52 ` [gentoo-dev] " Alexis Ballier

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=201402161758.43311.dilfridge@gentoo.org \
    --to=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