Add starfetch to package managers repositories

[dannydorazio]

Hi! I love starfetch and can't wait to see it grow. I was wondering if you had looked at publishing to homebrew? This would make it much easier to both install and update on macOS. Thanks for your consideration!

https://docs.brew.sh/Adding-Software-to-Homebrew

[Haruno19]

Thank you! I was already considering publishing starfetch to Homebrew in the future. Maybe I'll make the code more efficient and add some more constellation, and then I'll add it to Homebrew!

[mBaratta96]

Thank you for this wonderful tool! I would also like to suggest adding a repository for Linux to easily receive updates.

[Haruno19]

Now that the code has been revised, I'm currently looking into adding starfetch to Hombrew and other repositories. I'm still very new to this so I have to figure out how to do so.

In the meantime, a Pull Request to add starfetch to Nixpkgs has already been opened here thanks to user papojari.

[tildethinexxbisense]

how's the progress going? I have plenty of people who would use it if its on the APT because they're too afraid of building from source lol!

[Haruno19]

Yeah I’m so sorry it’s taking long! I’m now writing the formulae file to add it to homebrew but there’s still something wrong… I’m totally clueless with this kind of things, I’m sorry :(

[auroraanna]

@06kellyjac would like git versioning for packaging

[06kellyjac]

Not required but advised. This is what I put in the review

Since the maintainer is interested in this being packaged id advise they tag a version 0.0.1
People are more likely to package a release than a commit

[Haruno19]

So, I have to create a release tagging it as version 0.0.1?
(I'm very sorry for my ignorance about this)

[auroraanna]

You don't have to but it would be nice. It also doesn't have to be 0.0.1.

[06kellyjac]

@papojari is exactly right

---

Just some extra detail. A tag is a git feature a bit like a branch fixed in time. A github release can then be created from a tag if you want but just a tag is enough for us

Also I suggested 0.0.1 as a first version due to something called SemVer all the 0.X.X versions can have breaking changes, once you have a numbered release like 1.0.0 or 2.4.3 people might expect there to be "no breaking changes" at least until that first number increases again

https://semver.org/

Heres how to make a tag

https://stackoverflow.com/questions/18216991/create-a-tag-in-a-github-repository