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
