I suggest to break up the media-fonts/lohit-fonts package into sub-packages. According to this bug report https://bugzilla.redhat.com/show_bug.cgi?id=781466, newer tarballs for lohit-fonts are no longer released but they are for the individual fonts which are contained in the package. Version 2.5.0 for all the fonts were released in September 2011 but lohit-fonts hasn't been updated from 2.4.2 since September 2009. Also, breaking up the package would allow users to install only the fonts they need and not all of them contained in the lohit-fonts tarball. Currently, these are the fonts that are provided by the project, Assamese, Bengali, Devanagari (enables Hindi, Kashmiri, Konkani, Maithili, Marathi, Nepali, Sindhi), Gujarati, Kannada, Malayalam, Oriya, Punjabi, Tamil, and Telugu.
The fedora RPMs install these fonts in separate directories for every font, eg. the font lohit-assamese is installed in /usr/share/fonts/lohit-assamese.
Created attachment 312837 [details] lohit-assamese-2.5.1.ebuild Here are ebuilds derived from the original lohit-fonts ebuild for the 12 fonts. The fonts are installed in /usr/share/fonts/indic/${PN}.
Created attachment 312839 [details] lohit-bengali-2.5.1.ebuild
Created attachment 312841 [details] lohit-devanagari-2.5.1.ebuild
Created attachment 312843 [details] lohit-gujarati-2.5.1.ebuild
Created attachment 312845 [details] lohit-kannada-2.5.1.ebuild
Created attachment 312847 [details] lohit-malayalam-2.5.1.ebuild
Created attachment 312849 [details] lohit-marathi-2.5.1.ebuild
Created attachment 312851 [details] lohit-nepali-2.5.1.1.ebuild
Created attachment 312853 [details] lohit-oriya-2.5.1.ebuild
Created attachment 312855 [details] lohit-punjabi-2.5.1.ebuild
Created attachment 312857 [details] lohit-tamil-2.5.0.ebuild
Created attachment 312859 [details] lohit-telugu-2.5.1.ebuild
Created attachment 316587 [details] lohit-tamil-2.5.1.ebuild
Created attachment 316589 [details] lohit-tamil-classical-2.5.1.1.ebuild
I think we should go ahead and commit these
Well, it took us three years... but it's finally done!
*** Bug 436158 has been marked as a duplicate of this bug. ***