Dog disabled on Homebrew

[torfason]

I just tried installing dog using Homebrew and received the following error message:

$ brew install dog
Error: dog has been disabled because it is not maintained upstream! It was disabled on 2024-08-01.

It's a bummer, I have no idea about what their process is for determining this, but thought the maintainer(s) might like a heads-up since it seems to be recent. ❤️

[sh-cho]

Unfortunately, dog's author @ogham is not reachable for a few years, and I suppose there's no maintainer for this repository. Other project made by him is forked and maintained there, for example exa is forked to eza-community/eza.

So maybe it's time to move on to successor, for example doge. I don't really know which one is mainly used.

[torfason]

Thanks for the update! Did some research, seems like it was deprecated first and then disabled:

• Commit that disabled:
  • https://github.com/Homebrew/homebrew-core/commit/3f49dbdfafd784ed71fee7131e9a7c705a2b2a3e
• Commit that deprecated:
  • https://github.com/Homebrew/homebrew-core/commit/104c6e5044d610266533673e364378e13ecc4881

Deprecating commit also adds note regarding #98 which seems to be the trigger (and when not addressed it got disabled).

• doge is a nice clone, but not on Homebrew
• doggo is not a clone, but "It's totally inspired by dog", it is written in go and available on Homebrew

It would be nice if the eza model could be applied, perhaps with doge becoming a community driven version of dog.

[Dj-Codeman]

It would be nice if the eza model could be applied, perhaps with doge becoming a community driven version of dog.

You know, If I were smart I would have named it dog_community. I Haven't renamed a repo in Gh before so I have to idea what if any repercussions there might be but I'll look into it.

[torfason]

Sounds great. I don't know any issues with renaming a repo in GitHub, I think you can set forward, similar to happens with:

https://github.com/smbache/import

which has been moved to a different repo.

Also, I believe providing a formula that provides the dog executable might be acceptable for Homebrew in this case (and avoid the currently somewhat polarising doge name). However, the number of forks on the doge repo is probably too low for it to be accepted:

https://docs.brew.sh/Acceptable-Formulae#not-a-fork-usually

But an alternative tap might be useful for people ...

[mwarkentin]

I found doggo which looks similar to dog and is available on brew: brew install doggo

❯ doggo github.com
NAME            TYPE    CLASS   TTL     ADDRESS         NAMESERVER
github.com.     A       IN      7s      140.82.112.3    192.168.1.254:53

[AndreaCicca]

Deprecating commit also adds note regarding #98 which seems to be the trigger (and when not addressed it got disabled).

• doge is a nice clone, but not on Homebrew
• doggo is not a clone, but "It's totally inspired by dog", it is written in go and available on Homebrew

It would be nice if the eza model could be applied, perhaps with doge becoming a community driven version of dog.

Thanks for the alternatives, doggo is an interesting project.

It would be nice if the eza model could be applied, perhaps with doge becoming a community driven version of dog.

You know, If I were smart I would have named it dog_community. I Haven't renamed a repo in Gh before so I have to idea what if any repercussions there might be but I'll look into it.

It would be nice if someone could add doge to Homebrew

[hynek]

doge is on Homebrew now (I came here to check out why :)).

[mschirrmeister]

You should also check out the q client. Supports most DNS/Protocol features.