Re: [gentoo-user] Is binary emerge equivalent to source emerge?

[Sascha Lucas]

There are a few open bugs related to binpkg handling.  Attached is a script 
that prints out the use flags of a binpkg (similar to emerge -pv output).  I 
you believe that you have discovered an unreported bug, then please file a 
new bug at bugs.gentoo.org.


I did fill a bug report. Bug #105231 if someone is interested.

Sascha.

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Is binary emerge equivalent to source emerge?

[Zac Medico]

Sascha Lucas wrote:
I've also had problems with --usepkg.  When it gives me problems, as a 
workaround, I force emerge to do what I want with emerge --usepkgonly 
--nodeps --oneshot for each and every binpkg that I want merged.  If I 
think that this may have broken something then afterwards I use 
"revdep-rebuild -p" to check linking integrity.



thats nearly the same like I do: emerge --usepkg --oneshot binpkgs.

So I assume, I'm not alone with this problem (--newuse & --usepkg & 
-uD). The question is, is there a missunderstanding or a bug?


Sascha.


There are a few open bugs related to binpkg handling.  Attached is a script 
that prints out the use flags of a binpkg (similar to emerge -pv output).  I 
you believe that you have discovered an unreported bug, then please file a new 
bug at bugs.gentoo.org.

Zac
#!/usr/bin/python

import sys
if len(sys.argv)!=2:
	print "usage: %s " % sys.argv[0]
	sys.exit(1)

sys.path = ["/usr/lib/portage/pym"]+sys.path
import xpak
mytbz2=xpak.tbz2(sys.argv[1])
myuse=mytbz2.getelements("USE")
myiuse=mytbz2.getelements("IUSE")
for use in myiuse:
	operator="-"
	if use in myuse:
		operator="+"
	sys.stdout.write( operator + use + " ")
print

Re: [gentoo-user] Is binary emerge equivalent to source emerge?

[Sascha Lucas]

I've also had problems with --usepkg.  When it gives me problems, as a 
workaround, I force emerge to do what I want with emerge --usepkgonly 
--nodeps --oneshot for each and every binpkg that I want merged.  If I think 
that this may have broken something then afterwards I use "revdep-rebuild -p" 
to check linking integrity.


thats nearly the same like I do: emerge --usepkg --oneshot binpkgs.

So I assume, I'm not alone with this problem (--newuse & --usepkg & -uD). 
The question is, is there a missunderstanding or a bug?


Sascha.
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Is binary emerge equivalent to source emerge?

[Zac Medico]

Sascha Lucas wrote:

  - -uD --newuse --usepkg world (binary if possible, else ebuild) does not
work very well


I've also had problems with --usepkg.  When it gives me problems, as a workaround, I 
force emerge to do what I want with emerge --usepkgonly --nodeps --oneshot for each and 
every binpkg that I want merged.  If I think that this may have broken something then 
afterwards I use "revdep-rebuild -p" to check linking integrity.

Zac
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Is binary emerge equivalent to source emerge?

[Sascha Lucas]

Hi Ian,


1) Does this seem like a sensible idea?  Will it generally work?
2) Will --usepkg --getbinpkg use binary packages for dependencies?
3) Is the resultant Portage database equivalent to source emerges, especially 
in respect of future --updates, --newuse, etc?

4) Am I right to use a Portage snapshot from the current machine?
5) Is this idea so close to the Catalyst idea that I should use its methods 
to achieve my aims?


I'm answering to your thread, because I'm also playing with binary merges. 
At the moment I'm not realy happy with it. I've played with catalyst/GRP, 
PORTAGE_BINHOST (aka --getbinpkg), PKGDIR via nfs (aka --usepkg).


Perhaps there is someone out there who can point me to some docs etc. Or 
correct my following statments:


to 1)
 - yes it will work
 - you have 3 choices how to build your binarys
   * GRP with catalyst (usefull if your USE-/CFLAGS-Falgs etc. on the
 build system and target system differ)
   * quickpkg from allready installed ebuilds
   * FEATURES="buildpkg" in make.conf (creates bin's on merge)
 - the last 2 are usefull if your USE-/CFLAGS-Flags are identical or do
   not differ much

 - what you need is:
   * portage-snapshot (can be done with catalyst)
   * stage3 from internet or actual build with catalyst
   * binarys build with USE-/CFLAGS-Flags you want on the target

to 2)
  - yes binarys are used for deps
  - --usepkg looks for binarys in PKGDIR=${PORTDIR}/packages
  - --getbinpkg looks for binarys on PORTAGE_BINHOST (I tried ftp)
  - both have a "only" variant which should use only binarys
  - the only-variants doesn't make me happy, because they seem to ignore
different USE-Flags

to 3)
  - if you mean /var/db/pkg then yes it's the same
  - updates seem to work (-kuD world)
  - -uD --newuse world (ebuild only) works
  - -uD --newuse --usepkg world (binary if possible, else ebuild) does not
work very well

to 4 and 5) may be something in my comments to 1-3.

Perhaps I'm doing something wrong then please tell me the better way.

THX,

Sascha.
--
gentoo-user@gentoo.org mailing list