FEATURES=binpkg-multi-instance causes an integer build-id to be
associated with each binary package instance. Inclusion of the build-id
in the file name of the binary package file makes it possible to store
an arbitrary number of binary packages built from the same ebuild.
Having multiple
Extend the _pkg_str class with build_id, build_time, file_size, and
mtime attributes. These will be used to distinguish binary package
instances that have the same cpv. Package sorting accounts for
build_time, which will be used to prefer newer builds over older builds
when their versions are
FEATURES=binpkg-multi-instance causes an integer build-id to be
associated with each binary package instance. Inclusion of the build-id
in the file name of the binary package file makes it possible to store
an arbitrary number of binary packages built from the same ebuild.
Having multiple
Support profile-formats = build-id setting for layout.conf. When
this 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
Add a test case to verify that emerge --rebuilt-binaries works with
binpkg-multi-instance. This relies on the fact that binary packages of
the same version are ordered by BUILD_TIME, so that the latest builds
are preferred when appropriate.
---
pym/portage/tests/resolver/ResolverPlayground.py |
Duncan posted on Wed, 18 Feb 2015 03:40:35 + as excerpted:
Reading this gave me a distinct sense of deja vu reading this. ... =:^P
Crossed in the mail. Already corrected in the new series. =:^)
--
Duncan - List replies preferred. No HTML msgs.
Every nonfree program has a lord, a
Joshua Kinard posted on Tue, 17 Feb 2015 12:46:12 -0500 as excerpted:
On 02/16/2015 13:01, Rich Freeman wrote:
On Mon, Feb 16, 2015 at 11:02 AM, Joshua Kinard ku...@gentoo.org
wrote:
On 02/16/2015 09:04, Rich Freeman wrote:
Maybe another approach is to just ditch
per-file copyrights
Remove unused binarytree _remove_symlink, _create_symlink,
prevent_collision, _move_to_all, and _move_from_all methods. These are
all related to the oldest PKGDIR layout, which put all of the tbz2
files in $PKGDIR/All, and created symlinks to them in the category
directories. The $PKGDIR/All
Pacho Ramos posted on Mon, 16 Feb 2015 14:34:50 +0100 as excerpted:
The current policy of maintainers dropping keywords after 90 days is
simply not applied because it leads up to that maintainer needing to
kill himself that keyword and ALL the reverse deps keywords and, then,
all that effort
On Tue, Feb 17, 2015 at 9:19 PM, Duncan 1i5t5.dun...@cox.net wrote:
Since gentoo lacks this sort of formal signed-off policy and in fact has
yet to move to git where it could be most easily tracked and enforced
(let alone such a policy created and formally agreed in the first place),
the
On Mon, 16 Feb 2015 06:39:51 -0500
Mike Frysinger vap...@gentoo.org wrote:
the policy is not it must be Gentoo copyright, but it must have a
header that says Gentoo copyright even though there's no legal basis
for it.
Correct, but I have my doubts about the allegedly wobbly legal basis. I
do
On 18/02/15 08:40, Jeroen Roovers wrote:
I seem to recall the developer quizzes may have had (or indeed
requested) some more information on this matter.
The test ebuild focuses on this topic.
signature.asc
Description: OpenPGP digital signature
On Wed, 11 Feb 2015 11:56:37 -0700 Christoph Junghans wrote:
2015-02-11 11:14 GMT-07:00 Andrew Savchenko birc...@gentoo.org:
Hello,
attached patch adds Fortran compiler to Gentoo override rules in
cmake-utils.eclass the same way C/C++ compilers are added.
This change is needed because
On 02/17/2015 10:42 AM, Brian Dolbec wrote:
overall, there is no way I know the code well enough to know if you
screwed up. But the code looks decent, so...
My only questions are:
pym/portage/dbapi/bintree.py:
You removed several functions from the binarytree class and essentially
On Tue, 17 Feb 2015 11:26:27 -0800
Zac Medico zmed...@gentoo.org wrote:
On 02/17/2015 10:42 AM, Brian Dolbec wrote:
overall, there is no way I know the code well enough to know if you
screwed up. But the code looks decent, so...
My only questions are:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/02/15 18:34, Brian Dolbec wrote:
SURE! just reply to the EASY one ;)
The other ones will take me a bit longer. Sorry.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 17 Feb 2015 16:02:47 +0100
Alexander Berntsen berna...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
LGTM. Go ahead push.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN
On Tue, 17 Feb 2015 00:37:12 -0800
Zac Medico zmed...@gentoo.org wrote:
FEATURES=binpkg-multi-instance causes an integer build-id to be
associated with each binary package instance. Inclusion of the
build-id in the file name of the binary package file makes it
possible to store an arbitrary
On 02/16/2015 13:01, Rich Freeman wrote:
On Mon, Feb 16, 2015 at 11:02 AM, Joshua Kinard ku...@gentoo.org wrote:
On 02/16/2015 09:04, Rich Freeman wrote:
I do think that moving to a cleaner policy makes a lot of sense. The
problem is that doing this sort of thing right potentially involves a
On Tue, 17 Feb 2015 00:37:13 -0800
Zac Medico zmed...@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
On 02/17/2015 10:58 AM, Brian Dolbec wrote:
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
On 02/17/2015 11:56 AM, Brian Dolbec wrote:
On Tue, 17 Feb 2015 11:26:27 -0800
Zac Medico zmed...@gentoo.org wrote:
On 02/17/2015 10:42 AM, Brian Dolbec wrote:
overall, there is no way I know the code well enough to know if you
screwed up. But the code looks decent, so...
My only
Since commit f1c1b8a77eebf7713b32e5f9945690f60f4f46de, binarytree
regenerates the 'Packages' index unnecessarily, due to missing REQUIRES
and PROVIDES entries. These entries are not required, so use default
empty values in order to avoid the unnecessary regeneration.
Fixes: f1c1b8a77eeb (Generate
FEATURES=binpkg-multi-instance causes an integer build-id to be
associated with each binary package instance. Inclusion of the build-id
in the file name of the binary package file makes it possible to store
an arbitrary number of binary packages built from the same ebuild.
Having multiple
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,
25 matches
Mail list logo
