After discussing crosscompiling via -B options in the forum, I took a shallow look at /usr/bin/emerge and found that it is possible to set FEATURES="buildpkg" but not to set FEATURES="buildpkgonly" which might be handy for situations like the one decribed in the forum. This shouldnt be too hard to implement. BTW as another bug files buildpkgonly is missing in the man-page.
man page has been fixed in cvs for some time
Hmm, how would this work with dependencies that need to be installed ?
> Hmm, how would this work with dependencies that need to be installed ? dependencies should be compiled too as packages. This can be prevented with --nodeps.
I meant that the dependencies needs to be installed or the package won't find header files, libraries, needed tools, ... So should the dependencies get merged, then building the .tbz2 for the wanted package and then unmerging the package or what ? Or should portage just abort like emerge -B when dependencies are not met ?
Should portage just abort like emerge -B when dependencies are not met ? Yes. I think that will do.
The code is still in emerge. # Always create packages if FEATURES=buildpkg # Imply --buildpkg if --buildpkgonly if ("buildpkg" in portage.features) or ("--buildpkgonly" in myopts): if "--buildpkg" not in myopts: myopts.append("--buildpkg") Either it's going to get done and we can merge changes ( bail if deps aren't installed ) or it won't be and we can close and someone can reopen if necessary. Most poeple use crossdev ( or related ) and not portage for this anyway, so I'm not sure how much use it would get.
Closing this as it doesn't seem useful. FEATURES="buildpkgonly" is pretty much exactly the same as alias emerge='emerge -B'. Same argument could be used for buildpkg, but either that'll go or support for buildpkgonly will come incidentally. Either way, there are much better ways that cross compiling could be supported.
