When you say ut checks CHOST/keywording, where are those definitions
stored for the binary pkg?
I see one instance of CHOST in the 'Packages' index on the BINHOST. Is
that the variable emerge is comparing against? If not, where is it? the
tbz itself holds just the binaries.
Manually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Duft wrote:
Hi!
I have a quick question: is --nodeps supposed to still merge packages in
the right order?
Yes. The attached patch should fix it. Thanks for reporting.
- --
Thanks,
Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11
On Mon, 2009-04-20 at 08:35 +0200, Markus Duft wrote:
Hi!
I have a quick question: is --nodeps supposed to still merge packages in
the right order?
my specific problem is, that when i do this:
emerge -pv --noreplace --oneshot --nodeps \
sys-devel/gcc-config \
sys-devel/gcc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amit Dor-Shifer wrote:
When you say ut checks CHOST/keywording, where are those definitions
stored for the binary pkg?
It's appended to the tail end of the tbz2, in xpak format (see `man
5 xpak`).
I see one instance of CHOST in the 'Packages'
On Mon, 2009-04-20 at 02:14 -0700, Zac Medico wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Duft wrote:
Hi!
I have a quick question: is --nodeps supposed to still merge packages in
the right order?
Yes. The attached patch should fix it. Thanks for reporting.
cool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Duft wrote:
cool thanks :) so this patch makes portage merge in the order given on
the command line? this means it's the users fault if packages are in the
wrong order?
Right.
shouldn't portage do the same thing as with --nodeps,
except
