On Thu, 22 Jan 2015 16:43:32 +0800, Sam Bishop wrote: > I'll quote from the binpkg docs: > >> Next to these, portage will check if the binary package is built > >> using the same USE flags as expected on the client. If a package is > >> built with a different USE flag combination, portage will either > >> ignore the binary package (and use source-based build) or fail, > >> depending on the options passed on to emerge > > So I'm fairly sure that implies they can coexist based on the > directory structure. - > http://wiki.gentoo.org/wiki/Binary_package_guide#The_PKGDIR_layout
The package name is the same as the ebuild name but with a .tbz2 extension, so how could portage cope with multiple variants with different USE flags when there is only one name? There can be only one package per ebuild and either the USE flags match exactly or they do not. You could get away with this with a limited set of profiles by having a different $PKGDIR for each profile but to do it with random combinations would require some sort of middleware to handle the requests and place the specified packages where portage expects to find them. I think the check for USE flags is done using the IUSE and USE settings in the package metadata, so even if a USE flag you don't use is added to an ebuild, the package will no longer match. ISTR having to hack metadata in /var/db in the past to avoid a rebuild of *Office. -- Neil Bothwick When companies ship Styrofoam, what do they pack it in?
pgppgIhzUwDYu.pgp
Description: OpenPGP digital signature
