You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How do we handle font binary releases that are collected into archives such as .zip, .tar.gz?
This is a twofold qusetion;
A zip file containing all the necessary files along with the fontpackage.toml will also validate as a fontpackage without any attachment to git? If so how do we facilitate projects releasing binaries collected into archives?
If yes, we can check the releases artrfacts for .fontpkg for each repo and just grab that?
Need to think about the mechanics for unique names for packages and a central directory to clarify these.
The text was updated successfully, but these errors were encountered:
How do we handle font binary releases that are collected into archives such as .zip, .tar.gz?
This is a twofold qusetion;
fontpackage.toml
will also validate as afontpackage
without any attachment to git? If so how do we facilitate projects releasing binaries collected into archives?.fontpkg
for each repo and just grab that?Need to think about the mechanics for unique names for packages and a central directory to clarify these.
The text was updated successfully, but these errors were encountered: