Hi List,
can some explain this? Machine A+B have identical make.conf (expect in 3
USE-falgs), /etc/portage/*, /usr/portage, profile.
Machine A:
- FEATURES=buildpkg
- added USE-flag samba
- emerge -uD --newuse world
* builds new samba package
* rebuilds some packages (kdebase, cups,
On Wed, 2005-09-07 at 18:33 +0200, Sascha Lucas wrote:
Hi List,
can some explain this? Machine A+B have identical make.conf (expect in 3
USE-falgs), /etc/portage/*, /usr/portage, profile.
Machine A:
- FEATURES=buildpkg
- added USE-flag samba
- emerge -uD --newuse world
*
Machine B:
- mount PGKDIR of machine A via nfs to PGKDIR on machine B
- added USE-flag samba
- emerge -uD --newuse --usepkg world
* merges binary samba
* does not merge anything else (no binary, no ebuild )
It would be nice if I understand why emerge won't remerge binary packages
Sascha Lucas wrote:
Hi List,
Machine B:
- mount PGKDIR of machine A via nfs to PGKDIR on machine B
- added USE-flag samba
- emerge -uD --newuse --usepkg world
* merges binary samba
* does not merge anything else (no binary, no ebuild )
It would be nice if I understand
If you do --pretend --verbose, does it show the changed USE flags for
the packages? Not sure if 'world' does this, but you could try the
individual packages that you expect to be rebuilt. IIRC, it appears in
green (on a colour screen...) with a + and * next to the USE flag.
emerge -uD
Sascha Lucas wrote:
emerge -1 --usepkg --pretend --verbose pkg_spec_from_equery
then the change in USE-Flags are showen and my _correct_ binarys are used.
There's probably a good reason for it being the way it is, but it
doesn't sound as transparent as we might like.
A further
emerge -1 --usepkg --pretend --verbose pkg_spec_from_equery
then the change in USE-Flags are showen and my _correct_ binarys are used.
There's probably a good reason for it being the way it is, but it
doesn't sound as transparent as we might like.
yes may be... if so, I would like to know
There is no meta-info AFAIK in a binary .tar.gz, so portage does NOT
know what CFLAGS, or USE flags it is built with.
Go ahead, use quickpkg to make a binary tarball of any package on your
system, then look tat the tarball. There is nothing to indicate USE or
CFLAGS.
If you want to install
Bugger, after reading Sacha's last post and trying tbz2tool -split
package.tbz2 I realise that the meta info is there, quite a lot of it!
You certainly don't get to see it parsing the file with mc
I was wrong, my apologies.
A tool to better parse that metainfo out of binary packages would be
Nick Rout wrote:
There is no meta-info AFAIK in a binary .tar.gz, so portage does NOT
know what CFLAGS, or USE flags it is built with.
Go ahead, use quickpkg to make a binary tarball of any package on your
system, then look tat the tarball. There is nothing to indicate USE or
CFLAGS.
If you
On Wed, 07 Sep 2005 18:02:49 -0700
Zac Medico wrote:
The metadata is appended to the end of the tbz2 file. I guess you didn't see
my email earlier today which included a script that extracts the use flags.
http://marc.10east.com/?l=gentoo-userm=112613409500463w=2
Zac
err yes, see my
11 matches
Mail list logo
