>>>>> On Fri, 23 Mar 2018, Francesco Riosa wrote: > Il 23/03/2018 10:48, Ulrich Mueller ha scritto: >> Conceptually that makes no sense. sys-devel/gcc is the name of an >> upstream package, so what does it even mean to mask it in one >> repository but not in another? If it's the same package, then it >> should behave in the same way, regardless of the repository its >> ebuild it hosted in (or the package being installed, in which case >> it is no longer in an ebuild repository).
>> If it is a different package however, then it should have a >> different name. > Sorry to say it bluntly but this make no sense at all, even changing > a USE flag make the package behave wildly differently. Right, So you want USE dependencies, which we have. Nothing stops a package in an overlay from having additional USE flags. > Once we agree that an upstream (complex enough) package may have > different incarnations two ebuilds from different maintainers may > please differently the user. Still, masking is the wrong way to express such preferences. If you package.mask sys-devel/gcc then you say that something is wrong with that package. Which I believe is not what you want to express here. Ulrich
pgpInHKd1i4Yn.pgp
Description: PGP signature
