On 09/13/2011 01:26 AM, Michael Schreckenbauer wrote:
On Tuesday, 13. September 2011 01:11:39 Nikos Chantziaras wrote:
[...]
You cannot provide a slot - you provide a package - freetype in this
case. A slot is a gentoo specific thing.

So is package.provided :-)

Of course :) Point is, you provide a package from the outside world, you tell
that portage via package.provided. In the outside world, there is no slot. So
you cannot provide slots.

I think Alan actually provided a more correct POV, namely that package.provided was never updated to consider slots. If in the "outside world" there are no slots, then portage shouldn't have introduced that feature in the first place. But it did, and the package.provided mechanism was never updated.


Say, you had freetype-2.x in your package provided and for some reason
you configured it to install to /usr/include/freetype,
/usr/lib/freetype and so on. What should emerge do, if you now emerge
freetype:1? Install it and overwrite your provided package?

Yes.  It should do exactly that.  Because of lack of information, it
should assume that I know what I'm doing.

Fortunately, it does exactly that :-)  The original point of my post is
why it works with "emerge foo-version" but not with "emerge foo:slot".

Yes, it does that. In my opinion, that behaviour is not correct.

I think, you are "abusing" package.provided for something, that should be
handled by a local overlay with patched freetype-ebuilds.

I'm pretty sure you know very well by now that forking the portage tree isn't a Gentooer's idea of a great time ;-) We use Gentoo's tools to their fullest in order to lower burden and overhead, not raise it.

Forking my own ebuild means I need to maintain it; forever and ever. And stuff like that will keep piling up over time, leading to a big, magnificent pile of unmaintainable mess, leading to a bad experience and the question of I use Gentoo in the first place if all it will give me is annoyance and stress.

On the other hand, if a single line in package.provided does the job just as well, oh hell, I'm going for that one instead.


Reply via email to