Search Criteria
Package Details: otf-league-fonts 1:0-4
Package Actions
| Git Clone URL: | https://aur.archlinux.org/league-fonts.git (read-only, click to copy) |
|---|---|
| Package Base: | league-fonts |
| Description: | A package depending on all the fonts from The League of Moveable Type |
| Upstream URL: | https://www.theleagueofmoveabletype.com |
| Licenses: | OFL |
| Submitter: | eeva |
| Maintainer: | alerque (lightdot) |
| Last Packager: | alerque |
| Votes: | 9 |
| Popularity: | 0.000000 |
| First Submitted: | 2016-02-15 01:07 (UTC) |
| Last Updated: | 2024-03-27 22:25 (UTC) |
Dependencies (6)
- otf-chunkAUR
- otf-fanwoodAUR
- otf-junctionAUR
- otf-league-gothicAUR
- otf-league-spartanAUR (otf-league-spartan-gitAUR)
- otf-ralewayAUR (otf-raleway-gitAUR)
Latest Comments
alerque commented on 2020-06-12 20:26 (UTC)
@TheGoliath Please don't flag things as out of date that you don't use and don't know the versioning scheme. This is a meta package without an upstream version.
alerque commented on 2020-03-19 20:49 (UTC)
@lightdot It took a long time but I finally did hear back. We're supposed to have a video chat this week to talk through cleanup of LMT's git repos. Versioning will be on my agenda.
lightdot commented on 2018-03-06 04:32 (UTC)
I wish upstream would actually make proper releases... Have you perhaps heard back from them?
Also, the original packager made a questionable versioning choice that took us into thousands (version = packaging date). The only reason I went with a similar approach with ttf-league-mono (version = release date) is to remain vaguely consistent.
We can't switch to the date of the last release for all of them, since that would mean going to a lower version number for those packaged back in 2016... and if we switch all of them to the last update date, we don't really gain anything for the users, IMHO. The damage has already been done.
I think using an epoch and fixing this properly is the thing to do, but this makes sense only if upstream actually chooses a release version of some kind... So, I'm inclined to simply let versions be as they are now, as a temporary solution until something changes at the source. What do you think?
Anyway, I added you as a co-maintainer for all other lmt-fonts, just please discuss any major changes before going ahead. I'll do the same for your lmt packages, naturally.
alerque commented on 2018-02-24 08:06 (UTC)
@lightdot Added.
I was actually planning on picking up the League font packages and had been cleaning them up and adopting them as well. I got distracted for a couple days. I also emailed the League about possibly helping them fix some inconsistencies in their upstream repos I ran into while doing this, but haven't heard back yet. Maybe we can co-maintain the assorted Leage related packages?
One thing I'd like to fix is there is no consistent versioning across all the packages (hence making the version on this meta package pretty arbitrary). Any ideas on that? Date them all based on last update or release?
lightdot commented on 2018-02-22 18:18 (UTC)
Please add ttf-league-mono to dependencies, I've just packaged it.
BTW, I've picked up all other The League of Moveable Type font packages that were orphaned and cleaned up the PKGBUILDs. I'd gladly co-maintain the league-fonts and ttf-league-script-number-one if you wish.
milouse commented on 2016-03-14 23:45 (UTC)