Closed moschlar closed 9 years ago
I'm not sure that this would make much sense. In principle, the scripts are feature complete and changes are mainly for new font versions and convenience. Thus, if the package for one font has been installed and it works, It probably doesn't make much sense to install it again except when there are new features in the LaTeX font package. This is indicated by a new revision for that font.
Therefore, I would suggest to have ebuilds with the version tags for each font and to have a live git version. What do you think?
I did that, at first. But the problem is that in the ebuild I need quite "a lot" of code to extract the otf files from the Adobe Reader tarball. If I have two different ebuilds, I need to duplicate that code... It's not really that big of an issue, I just wanted to avoid code duplication at all costs :frowning: . I'll reconsider it...
Right now, you tag releases per indivudal font, could you consider also using some universal versioning scheme? So that I can fetch the tarball more easy?