app-text/texlive:=[l10n_en?,l10n_fr?,l10n_it?,l10n_ja?,l10n_nl?,l10n_pl?] This dep is wrong. app-text/texlive is just a metapackage for user's convenience. You need to depend on specific texlive packages that your ebuild actually needs.
Addressed for kicad-doc-4.0.6 in PR 4991.
Except that makes the ebuild fail on a bunch of languages. I need texlive to be installed with the language flag enabled that is also used for this ebuild. Examining the texlive ebuild I can see that the language packs are dependant on the texlive version and there is no other texlive package I can pull it that has language flags. This will have to stay. Unless someone has a suggestion how to solve it, I will mark this bug as a WONTFIX and there is no other solution to it.
You have to depend directly on the exact packages your package needs.
Okay, if that's the policy. I have update the PR with exact dependencies.
(In reply to Michał Górny from comment #0) > app-text/texlive:=[l10n_en?,l10n_fr?,l10n_it?,l10n_ja?,l10n_nl?,l10n_pl?] > > This dep is wrong. app-text/texlive is just a metapackage for user's > convenience. You need to depend on specific texlive packages that your > ebuild actually needs. Note that it is sometimes ok and expected for ebuilds to depend on the metapackage: Think about a latex GUI with a 'compile' button. Compilation will fail if user builds a document using packages that are not installed. In that case, we expect ebuilds to depend on app-text/texlive to specify "anything tex-related" and users to set proper useflags on app-text/texlive for their intended use. If your package needs specific latex packages that are known in advance then you should depend on them directly in order to avoid users having to fine tune package.use for app-text/texlive when a simpler direct dep in the ebuild would have had the same effect. A good rule of thumb could be that 'app-text/texlive' deps are ok but usedeps on it are forbidden.
