admin/brew
1
0
Fork 0
Code Issues Packages Projects Releases 6 Wiki Activity

How-to-Create-and-Maintain-a-Tap: note brew tap-new.

Browse Source 
A bit of a glaring omission I noticed.
This commit is contained in:
Mike McQuaid 2019-10-10 11:22:41 +01:00
parent fb87225479
commit 212c197886
No known key found for this signature in database
GPG Key ID: 48A898132FD8EE70
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/How-to-Create-and-Maintain-a-Tap.md
View File

@ -13,6 +13,9 @@ If hosted on GitHub, we recommend that the repository’s name start with
`homebrew-` so the short `brew tap` command can be used. `homebrew-` so the short `brew tap` command can be used.
See the [manpage](Manpage.md) for more information on repository naming. See the [manpage](Manpage.md) for more information on repository naming.
The `brew tap-new` command can be used to create a new tap along with some
template files.
Tap formulae follow the same format as the core’s ones, and can be added at the Tap formulae follow the same format as the core’s ones, and can be added at the
repository’s root, or under `Formula` or `HomebrewFormula` subdirectories. We repository’s root, or under `Formula` or `HomebrewFormula` subdirectories. We
recommend the latter options because it makes the repository organisation recommend the latter options because it makes the repository organisation