From: Zac Medico <zmedico@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>, "Zac Medico" <zmedico@gentoo.org>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] Support @profile package set for bug #532224
Date: Thu, 11 Dec 2014 00:38:11 -0800 [thread overview]
Message-ID: <548957F3.6070401@gentoo.org> (raw)
In-Reply-To: <20141211092559.043da1b1@pomiot.lan>
On 12/11/2014 12:25 AM, Michał Górny wrote:
> Dnia 2014-12-10, o godz. 18:08:00
> Zac Medico <zmedico@gentoo.org> napisał(a):
>
>> Add support for a new @profile set which allows the profile to pull
>> in additional packages that do not belong to the @system set.
>>
>> The motivation to have @profile separate from @system is that
>> @system packages may have incomplete dependency specifications
>> (due to long-standing Gentoo policy), and incomplete dependency
>> specifications have deleterious effects on the ability of emerge
>> --jobs to parallelize builds. So, unlike @system, packages added to
>> @profile do not hurt emerge --jobs parallelization.
>>
>> Packages are added to the @profile set in the same way that they are
>> added to the @system set, except that atoms in the @profile set are
>> not preceded with a '*' character. Also, the @profile package set
>> is only supported when 'profile-set' is listed in the layout.conf
>> profile-formats field of the containing repository.
>
> PMS says PMs ought to ignore atoms without '*'. This means we can't use
> it without profile EAPI change, or other PMs will start losing packages.
It's hidden behind a layout.conf profile-formats flag, so it's beyond
the scope of PMS. Package managers should reject the profile if they
don't recognize the profile-formats flags that it declares.
--
Thanks,
Zac
next prev parent reply other threads:[~2014-12-11 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 2:08 [gentoo-portage-dev] [PATCH] Support @profile package set for bug #532224 Zac Medico
2014-12-11 2:27 ` vivo75
2014-12-11 2:35 ` Zac Medico
2014-12-11 7:48 ` Alexander Berntsen
2014-12-11 8:25 ` Michał Górny
2014-12-11 8:38 ` Zac Medico [this message]
2014-12-12 16:01 ` Rick "Zero_Chaos" Farina
2014-12-12 16:51 ` Zac Medico
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=548957F3.6070401@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=mgorny@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