Request for Help: Homebrew package maintainer

[cmang]

I would like for someone who has experience maintaining Homebrew packages, to maintain one for Durdraw.

I can pay you in ASCII Art and compliments.

Thank you.

[alexmyczko]

haha like the payment in ascii art, i will look into this

would stars and likes in other issues and github projects also work as payment?

[cmang]

would stars and likes in other issues and github projects also work as payment?

I think that can be arranged. 😄

[alexmyczko]

I would like a star here:

https://github.com/alexmyczko/ruptime
https://github.com/alexmyczko/autoexec.bat
blobject/agave#5 (comment)

And here will be the result:

https://github.com/alexmyczko/homebrew-mac

signed,
the github star dealers

[cmang]

Well, I already had ruptime starred... Consider them starred and high-fived.

I encourage everyone to star these fine repos and comment.

I am also finding myself a bit distracted by the code at: https://github.com/alexmyczko/modplug-tools

You rock, Alex. Thank you!

[alexmyczko]

sounds like a nomination for https://stars.github.com/

[alexmyczko]

more or less it's this: https://github.com/alexmyczko/homebrew-mac/blob/main/durdraw.rb
i hope to generate these without human resources at all. of course the install/test part are not working yet. i've just had a horrible experience with python (not the first, not the last), so if someone feels like filling in the blanks, go ahead..

[cmang]

i've just had a horrible experience with python (not the first, not the last),

Haven't we all? :)

The latest version of Durdraw can run in pure Python+standard library with no dependencies. The optional deps only help if you need GIF and PNG export, and even that's limited to CP437 and 16-color. I would not be offended by PIL and/or Ansilove dependencies being missing.

Would that make it easier?

[leviable]

@cmang I made a homebrew tap for you that does basically everything. You have three options to use it (I would recommend doing number 3):

1. Point people to my tap

brew tap leviable/durdraw
brew install durdraw

2. Copy everything (including the .github dir but not the .git dir) from my repo into your own repo. You will need to name your repo "cmang/homebrew-durdraw" (the homebrew- prefix is important), and you will need to replace every reference to leviable with cmang. I set mine up using method 3 below, and it did a lot for me under the hood, like configuring github actions and packages. I'm not 100% confident that simply copying the files will do all configuration needed. If you take this approach, your users will only need to:

brew tap cmang/durdraw
brew install durdraw

3. Create the tap yourself. It's actually quite easy and straightforward, which I just found out as this is the first time I've ever done it. Instructions to replicate what I did are as follows:

   1. Create a new repo in github. It MUST be named "homebrew-durdraw" for the brew tap command to work as intended
   2. Install homebrew. It works well with linux and macos, for both x86_64 and arm64
   3. Create the tap locally: brew tap-new --branch main --github-packages cmang/durdraw
      a. Note the instructions it spits out at the end. Copy and save those elsewhere so you can reference them later if needed.
   4. cd into the new directory. You can get the file path with brew tap-info cmang/durdraw
   5. You may need to set your remote git remote set-url origin git@github.com:cmang/homebrew-durdraw.git and your master/main branch origin
   6. Check out a new branch, strongly suggest not merging directly to master/main
   7. Create your new formula, using the link to the latest github release:

   brew create --python https://github.com/cmang/durdraw/archive/refs/tags/0.29.0.tar.gz --tap cmang/durdraw
   

   7. Copy the Formula/durdraw.rb from my repo to yours. You shouldn't need to make any changes
   8. At this point you can audit, test, and install the formula locally. It's helpful to do these locally before pushing, as CI will also do them, so its nice to know things are working before waiting on the CI cycle:

   brew audit durdraw --strict
   brew test durdraw
   brew install durdraw
   which durdraw  # should be in $(brew config | grep HOMEBREW_PREFIX)/bin
   durdraw -V
   

   9. Commit your changes and push git push origin <your branch>
   10. Open your github repo in a browser and create a pull request. Github actions should kick off at this point.
       a. If you encounter any failures, fix them locally and commit with --amend and force push the amended commit. as CI expects there to be one and only one commit
   11. Finally, when you are ready to merge, create/add a pr-pull tag to the PR, and CI will do the rest, including closing the PR and publishing everything to github packages. Check brew commands for other supported tags (pr-automerge, pr-publish, etc)
   12. At this point all your users need to do is tap and install

brew tap cmang/durdraw
brew install durdraw

13. When you release a new version in the durdraw repo, all you need to do for your homebrew repo is run brew bump-formula-pr and repeat the push/tag workflow. If you want to get even fancier you can setup triggers so that when you cut a release in the durdraw repo, a PR in this new homebrew repo gets automatically created.

Since your repo is quite popular, based on the number of stars and its distribution through other linux package managers, you could also try to get this Formula merged into homebrew-core. I would note, however, that since durdraw is based on neofetch, an unmaintained and deprecated package, the homebrew-core maintainers may not accept it on that basis alone.