Homebrew/cask-fonts will soon be deprecated #1635
Comments
|
Thank you for the information! 👍 I believe the change in our workflow will be easy. Was busy today and will be tomorrow, but I will come back to this on the weekend. |
|
Sounds good. I will keep an eye on this thread. Thank you! |
Finii
added a commit
that referenced
this issue
May 16, 2024
[why] The Cask-fonts repo has been incorporated into the main Cask repo. On releases we would use an obsolete repository to create the Cask into. The casks are now in a dedicated subdirectory (Casks/font) and under that we have one subdirectory for each font name starting character (to have a smaller number of files per directory I assume). [how] Change the repository path. Put part of the new (longer) path, the fixed part, just in the CI process, while the generator script takes care about the one-directory-per-startchar substructure. Fixes: #1635 Signed-off-by: Fini Jastrow <[email protected]>
Finii
added a commit
that referenced
this issue
May 16, 2024
[why] The Cask-fonts repo has been incorporated into the main Cask repo. On releases we would use an obsolete repository to create the Cask into. The casks are now in a dedicated subdirectory (Casks/font) and under that we have one subdirectory for each font name starting character (to have a smaller number of files per directory I assume). [how] Change the repository path. Put part of the new (longer) path, the fixed part, just in the CI process, while the generator script takes care about the one-directory-per-startchar substructure. Fixes: #1635 Signed-off-by: Fini Jastrow <[email protected]>
|
Closing as this migration has been finished for some time. Shout if you need anything @Finii! |
Finii
added a commit
that referenced
this issue
Nov 18, 2024
[why] The Cask-fonts repo has been incorporated into the main Cask repo. On releases we would use an obsolete repository to create the Cask into. The casks are now in a dedicated subdirectory (Casks/font) and under that we have one subdirectory for each font name starting character (to have a smaller number of files per directory I assume). [how] Change the repository path. Put part of the new (longer) path, the fixed part, just in the CI process, while the generator script takes care about the one-directory-per-startchar substructure. Fixes: #1635 Signed-off-by: Fini Jastrow <[email protected]>
Finii
added a commit
that referenced
this issue
Nov 18, 2024
[why] The Cask-fonts repo has been incorporated into the main Cask repo. On releases we would use an obsolete repository to create the Cask into. The casks are now in a dedicated subdirectory (Casks/font) and under that we have one subdirectory for each font name starting character (to have a smaller number of files per directory I assume). [how] Change the repository path. Put part of the new (longer) path, the fixed part, just in the CI process, while the generator script takes care about the one-directory-per-startchar substructure. Fixes: #1635 Signed-off-by: Fini Jastrow <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello 👋 . I'm a maintainer for the Homebrew project. I'm opening this issue to inform the nerd-fonts maintainers of the upcoming deprecation of Homebrew/cask-fonts. All fonts will be migrated to the main Homebrew/cask repo.
We will migrate all nerd-fonts to the main Homebrew/cask repo and introduce a redirect so existing users will seem seamlessly transitioned. I would like to work together to find a time the nerd-fonts release workflow can be updated, and migrate the fonts at the same time so there is no disconnect. Please let me know if there are any questions.
cc @Finii who I've worked with before on this.
The text was updated successfully, but these errors were encountered: