public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH 2/2] Add profile-formats=build-id (bug 150031)
Date: Tue, 17 Feb 2015 10:58:31 -0800	[thread overview]
Message-ID: <20150217105831.424731db.dolsen@gentoo.org> (raw)
In-Reply-To: <1424162233-25071-2-git-send-email-zmedico@gentoo.org>

On Tue, 17 Feb 2015 00:37:13 -0800
Zac Medico <zmedico@gentoo.org> wrote:

> When "profile-formats = build-id" is enabled in layout.conf of the
> containing repository, a dependency atom in the profile can refer
> to a specific build, using the build-id that is assigned when
> FEATURES=binpkg-multi-instance is enabled. A build-id atom is
> identical to a version-specific atom, except that the version is
> followed by a hyphen and an integer build-id.
> 
> With the build-id profile format, it is possible to assemble a system
> using specific builds of binary packages, as users of "binary"
> distros might be accustomed to. For example, an atom in the "packages"
> file can pull a specific build of a package into the @system set, and
> an atom in the "package.keywords" file can be used to modify the
> effective KEYWORDS of a specific build of a package.
> 
> Refering to specific builds can be useful for a number of reasons. For
> example, if a particular build needs to undergo a large amount of
> testing in a complex environment in order to verify reliability, then
> it can be useful to lock a profile to a specific build that has been
> thoroughly tested.
> 
> X-Gentoo-Bug: 150031
> X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=150031
> ---
>  man/portage.5                                      |   8 +-
>  pym/_emerge/is_valid_package_atom.py               |   5 +-
>  pym/portage/_sets/ProfilePackageSet.py             |   3 +-
>  pym/portage/_sets/profiles.py                      |   3 +-
>  pym/portage/dep/__init__.py                        |  35 +++++-
>  .../package/ebuild/_config/KeywordsManager.py      |   3 +-
>  .../package/ebuild/_config/LocationsManager.py     |   8 +-
>  pym/portage/package/ebuild/_config/MaskManager.py  |  21 +++-
>  pym/portage/package/ebuild/_config/UseManager.py   |  14 ++-
>  pym/portage/package/ebuild/config.py               |  15 ++-
>  pym/portage/repository/config.py                   |   2 +-
>  pym/portage/tests/dep/test_isvalidatom.py          |   8 +-
>  .../test_build_id_profile_format.py                | 134
> +++++++++++++++++++++
> pym/portage/util/__init__.py                       |  13 +- 14 files
> changed, 234 insertions(+), 38 deletions(-) create mode 100644
> pym/portage/tests/resolver/binpkg_multi_instance/test_build_id_profile_format.py
> 


class Atom()

 			if allow_repo is None:
 				allow_repo = True
+			if allow_build_id is None:
+				allow_build_id = True


these can be written as
  allow_repo = allow_repo or True
  allow_build_id = allow_build_id or True


Otherwise looks decent.

-- 
Brian Dolbec <dolsen>



  reply	other threads:[~2015-02-17 18:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  8:37 [gentoo-portage-dev] [PATCH 1/2] Add FEATURES=binpkg-multi-instance (bug 150031) Zac Medico
2015-02-17  8:37 ` [gentoo-portage-dev] [PATCH 2/2] Add profile-formats=build-id " Zac Medico
2015-02-17 18:58   ` Brian Dolbec [this message]
2015-02-17 19:37     ` Zac Medico
2015-02-17 19:58       ` Brian Dolbec
2015-02-17 18:42 ` [gentoo-portage-dev] [PATCH 1/2] Add FEATURES=binpkg-multi-instance " Brian Dolbec
2015-02-17 19:26   ` Zac Medico
2015-02-17 19:56     ` Brian Dolbec
2015-02-17 19:59       ` Zac Medico
2015-02-18  3:05       ` [gentoo-portage-dev] [PATCH 0/7] " Zac Medico
2015-02-18  3:05         ` [gentoo-portage-dev] [PATCH 1/7] binpkg-multi-instance 1 of 7 Zac Medico
2015-02-19 22:26           ` [gentoo-portage-dev] [PATCH 1/7 v2] " Zac Medico
2015-02-18  3:05         ` [gentoo-portage-dev] [PATCH 2/7] binpkg-multi-instance 2 " Zac Medico
2015-02-18  3:05         ` [gentoo-portage-dev] [PATCH 3/7] binpkg-multi-instance 3 " Zac Medico
2015-02-27 21:58           ` [gentoo-portage-dev] [PATCH 3/7 v2] " Zac Medico
2015-02-27 23:36           ` [gentoo-portage-dev] [PATCH 3/7 v3] " Zac Medico
2015-02-18  3:05         ` [gentoo-portage-dev] [PATCH 4/7] binpkg-multi-instance 4 " Zac Medico
2015-02-18  3:05         ` [gentoo-portage-dev] [PATCH 5/7] binpkg-multi-instance 5 " Zac Medico
2015-02-18  3:05         ` [gentoo-portage-dev] [PATCH 6/7] binpkg-multi-instance 6 " Zac Medico
2015-02-18  3:05         ` [gentoo-portage-dev] [PATCH 7/7] binpkg-multi-instance 7 " Zac Medico
2015-03-04 21:34         ` [gentoo-portage-dev] [PATCH 0/7] Add FEATURES=binpkg-multi-instance (bug 150031) Brian Dolbec
2015-02-18  3:40 ` [gentoo-portage-dev] Re: [PATCH 1/2] " Duncan
2015-02-18  3:46   ` Duncan

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=20150217105831.424731db.dolsen@gentoo.org \
    --to=dolsen@gentoo.org \
    --cc=gentoo-portage-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