{"push_id":576474310,"size":1,"distinct_size":0,"ref":"refs/heads/multi-binpkg-per-ebuild","head":"1d1620fdcc0c6e3b8e4a534cf16a6b478468eb3a","before":"2dba20bde2dbc7175b394207a99465dccfbb7f05","commits":[{"sha":"1d1620fdcc0c6e3b8e4a534cf16a6b478468eb3a","author":{"email":"a17fa1dcf5b7e2df0c563c7a30fa1870d6a8ff57@gentoo.org","name":"Zac Medico"},"message":"Add profile-formats=build-id\n\nWhen \"profile-formats = build-id\" is enabled in layout.conf of the\ncontaining repository, a dependency atom in the profile can refer\nto a specific build, using the build-id that is assigned when\nFEATURES=binpkg-multi-instance is enabled. A build-id atom is identical\nto a version-specific atom, except that the version is followed by a\nhyphen and an integer build-id.\n\nWith the build-id profile format, it is possible to assemble a system\nusing specific builds of binary packages, as users of \"binary\"\ndistros might be accustomed to. For example, an atom in the \"packages\"\nfile can pull a specific build of a package into the @system set, and\nan atom in the \"package.keywords\" file can be used to modify the\neffective KEYWORDS of a specific build of a package.\n\nRefering to specific builds can be useful for a number of reasons. For\nexample, if a particular build needs to undergo a large amount of\ntesting in a complex environment in order to verify reliability, then it\ncan be useful to lock a profile to a specific build that has been\nthoroughly tested.\n\nX-Gentoo-Bug: 150031\nX-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=150031","distinct":false,"url":"https://api.github.com/repos/zmedico/portage/commits/1d1620fdcc0c6e3b8e4a534cf16a6b478468eb3a"}]}