Any update?

[glypse]

Hi!

I've been looking for a font package manager for a while now, and stumbling onto your project (the only one I found, honestly) brung me a lot of joy. I would love to see this project growing, do you have any plans on working on it more? Support for variable fonts, releases from GitHub/GitLab/etc, a way to see outdated fonts and pick which to update, a release for non-rust users (ie binary per platform, Chocolatey for Windows, Homebrew for MacOS, ...)?

I'm personally very busy, but once I'll have more free time, I'd love to contribute :)

[tecc]

Apologies for the late reply! I'm not very active on GitHub so it usually takes a while before I notice things.

At some point I'd like to get back to this project, but right now I'm slightly preoccupied.
If (hopefully when) I get back to it I'd also have to raze the entire codebase to the ground first - this was an early project from when I had just started learning Rust, so the code is less idiomatic than I'd like it to be.

Regarding the specific features you mentioned (should I attempt to revive this project):

• Support for variable fonts: Absolutely. I don't remember the exact reason why it doesn't support variable fonts, but it really should.
• Releases from GitHub/GitLab: By this I assume you either mean including binaries with each release on the repository (i.e. https://github.com/tecc/fontpm/releases) or automating builds GitHub Actions. I'll be considering both: it would be nice.
• Releases for non-Rust users: Although my original intentions for the project was mainly for developers, this sounds nice. This also ties in with the previous point of automated builds and releases; if each release builds once for every platform, those artifacts can be repackaged for at least some platforms. Which platforms/package managers in particular would be a matter for later consideration.
• Outdated font detection: This would also be nice. It does require some research into how they're going to be managed (since FontPM would need to know what versions are installed), but that would probably be necessary either way.

I might do a quick restructure of the code into a viable foundation for future expansion soon but I can't spend too much time on it.
And I'll gladly accept any contributions (although preferably after I've cleaned up a bit, if I do).

(Edit: I am very tired writing this reply so I'm making a lot of mistakes, so I'm editing them to fix it)