Both media-fonts/fonts-misc-misc and media-fonts/font-cursor-misc install
So we have a record:
20:09 <@spyderous> Ticho: there isn't really a good solution to that, because
we need to regenerate those files for each package installed
to that directory
20:10 <@Ticho> spyderous: then don't install those files and have it generated
after all files are installed into image
20:10 <@Ticho> spyderous: ah, i see now
20:10 <@spyderous> people will complain about that too, because then the files
won't be owned by anything
20:10 <@Ticho> spyderous: isn't there something like collision protect mask?
20:11 <@spyderous> Ticho: nope
20:11 <@spyderous> at least not according to grep
20:12 <@spyderous> the optimal solution would be a pkg_postrm check whether any
font* packages are still installed, and if not, delete
20:12 <@spyderous> but that still feels like a hack
20:12 <@Ticho> that doesn't sound right
Is there any way to add ownership to a location/file so that collision-protect
no longer complains?
*** Bug 116626 has been marked as a duplicate of this bug. ***
*** Bug 116624 has been marked as a duplicate of this bug. ***
We've got a cleanup function in the modular eclass now so we can probably delete these files from IMAGE for any font types for which they will be autogenerated. That will prevent most of the ownership problems, although it will leave them unowned by any package so anyone querying them will be confused.
This could be mentioned in http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml to make it easier to migrate to modular X by deleting these files before starting emerge xorg-x11.
2 different font ebuilds shouldn't be installing the same /usr/share/fonts/ dir, at least thats an assumption we made with the fonts eclass. Can that be fixed ?
(In reply to comment #7)
> 2 different font ebuilds shouldn't be installing the same /usr/share/fonts/
> dir, at least thats an assumption we made with the fonts eclass. Can that be
> fixed ?
No, because we're installing to the same locations as the monolith did, so e.g. multiple packages install to 100dpi/ , multiple others to misc/ , etc. We need to do this to avoid breaking configurations and assumptions made by every X config tool in existence.
The answer in this case, I think, will be not providing fonts.* files at all in all cases where they can be autogenerated (non-CID, non-Speedo). This means they'll essentially be orphaned files, but the x-modular eclass has a function to take care of them if they're left over in an empty directory.
Fixed a couple of days ago.