We're actually using portage 2.1-r2 and INSTALL_MASK does exactly what
we need it to do for binary packages.
We're building binary packages from source and then install them into
the target using something like this:
INSTALL_MASK="$(cat "${CONFIG_DIR}/install-mask.txt")" ROOT="$
{ROOTFS}" emerge -Kv ${EBUILDS}
and it works just fine. "install-mask.txt" would contain everything
that we don't want in the target (quite some list), one item per line
such as:
*.h
*.hh
*.c
*.in
*.cpp
*.C
*.la
*.a
*README*
etc.
Also
INSTALL_MASK="$(cat "${CONFIG_DIR}/install-mask.txt")" ROOT="$
{ROOTFS}" emerge --info
displays INSTALL_MASK correctly.
I think I also tried the same concept with later versions of portage
and never had a problem (except when I had "*portage*" in my
INSTALL_MASK, because emerge uses /var/tmp/portage internally and this
seems to be affected by INSTALL_MASK, too).
Dirk
Hi everyone,
I'm in the process of installing a bunch of packages to make an EEE
pc root filesystem right now, and I've noticed that INSTALL_MASK is
not masking out the *.h files that I don't need.
After doing a bit of looking, I found this gentoo bug that seems to
be from portage-2.1_pre6
http://bugs.gentoo.org/show_bug.cgi?id=81025
I'm using portage-2.1.4.4 and I can only guess that INSTALL_MASK is
still not implemented for installing from binary packages.
Does anyone know if that is correct?
Cheers,
Chris
--
[email protected] mailing list
