[gentoo-portage-dev] How to hardmask all ebuilds from an overlay?

[gentoo-portage-dev] How to hardmask all ebuilds from an overlay?

[Pacho Ramos]

Hi!

My intention is prevent emerge from upgrading to testing versions from
an overlay instead of main portage tree. I thought that an option could
be make all ebuilds from that overlay hardmasked and, then, unmask
wanted packages manually by me

How could I do it?

Thanks a lot for the info :-)

Re: [gentoo-portage-dev] How to hardmask all ebuilds from an overlay?

[Zac Medico]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pacho Ramos wrote:
> Hi!
> 
> My intention is prevent emerge from upgrading to testing versions from
> an overlay instead of main portage tree. I thought that an option could
> be make all ebuilds from that overlay hardmasked and, then, unmask
> wanted packages manually by me
> 
> How could I do it?

Currently, the simplest solution might be to use an rsync command to
sync the specific packages that you want (or exclude the unwanted
packages) to a separate directory, and put the separate directory in
PORTDIR_OVERLAY instead of the original one.

Otherwise, the only alternative is to use package.mask and I'm
afraid that will not be very manageable give the current
capabilities. In the future we might add support to specify repo
names in dependency atoms, which will allow you to mask packages
from a specific repository.
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkmUaO4ACgkQ/ejvha5XGaMz+ACgxZvE+2lBFGDYr53AIaXXYMUr
TAIAoO8tL06S63gckMW24Lq45/EpuFAR
=cpkq
-----END PGP SIGNATURE-----

Re: [gentoo-portage-dev] How to hardmask all ebuilds from an overlay?

[Pacho Ramos]

El jue, 12-02-2009 a las 10:22 -0800, Zac Medico escribió:
> Currently, the simplest solution might be to use an rsync command to
> sync the specific packages that you want (or exclude the unwanted
> packages) to a separate directory, and put the separate directory in
> PORTDIR_OVERLAY instead of the original one.
> 
> Otherwise, the only alternative is to use package.mask and I'm
> afraid that will not be very manageable give the current
> capabilities. In the future we might add support to specify repo
> names in dependency atoms, which will allow you to mask packages
> from a specific repository.
> - --
> Thanks,
> Zac

OK, thanks for the recommendation :-)