Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider generating upstream metadata for fonts #37

Open
n7s opened this issue Apr 18, 2017 · 4 comments
Open

Consider generating upstream metadata for fonts #37

n7s opened this issue Apr 18, 2017 · 4 comments
Assignees

Comments

@n7s
Copy link
Contributor

n7s commented Apr 18, 2017

https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Fonts.html provides a metadata example file that distributions are starting to use to better classify fonts and make them available to users.

Longer-term, we should consider if smith can provide such metadata.

@n7s n7s self-assigned this Apr 18, 2017
@devosb
Copy link
Contributor

devosb commented Apr 18, 2017

Agree, this would be good. Until then, there is a partial solution already in place.

For font and other packages on packages.sil.org an AppStream metadata file (aka DEP-11, IIRC) should be generated by the server from the uploaded package. From the example above, I would guess such files would not contain the list of font names, as I don't see how such information could be extracted from the packaging.

When the script on packages.sil.org to generate the AppStream files was written, the author mentioned to me that there were no plans to add AppStream capability to PPAs. If that is still the case, then a fonts PPA could not contain this metadata.

@n7s
Copy link
Contributor Author

n7s commented Apr 18, 2017

What script on PSO are your referring to? I don't think this needs to be server-side but something that could become part of the tarball target.

@devosb
Copy link
Contributor

devosb commented Apr 19, 2017

I don't know the name of the script on PSO. It is the same script that Debian and/or Ubuntu uses. Bugs were found when testing the script on PSO, and patches sent to the upstream developer, who was interested in the fixes.

I agree this does not need to be server side. I merely wish to point out what was currently happening. I realize now when I said "should" above I meant I think the script is being run and generating AppStream metadata, not that the approach of having a script on the server is preferred.

@n7s
Copy link
Contributor Author

n7s commented Apr 19, 2017

OK, thanks for clarifying 👍

@nrsiward nrsiward changed the title Consider generating appstream metadata for fonts Consider generating upstream metadata for fonts Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants