Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homebrew formula disabled #475

Open
timnovis opened this issue Aug 12, 2020 · 13 comments
Open

Homebrew formula disabled #475

timnovis opened this issue Aug 12, 2020 · 13 comments

Comments

@timnovis
Copy link

steps

Try and install giter8 with homebrew as per the docs - brew install giter8

problem

Command outputs Error: giter8 has been disabled!

Looks like the formula has been disabled: https://github.com/Homebrew/homebrew-core/blob/master/Formula/giter8.rb#L11

expectation

giter8 should have installed successfully

@eed3si9n
Copy link
Member

Looks like it was disabled here - Homebrew/homebrew-core#58850

@anip-patel-exa
Copy link

I am also hitting the same issue. Is there any workaround for this?

@eed3si9n
Copy link
Member

The work around would be something like

curl -L https://search.maven.org/remotecontent?filepath=org/foundweekends/giter8/giter8-bootstrap_2.12/0.13.1/giter8-bootstrap_2.12-0.13.1.sh > ~/bin/g8
chmod +x ~/bin/g8

@MrPowers
Copy link

The new command is sbt new scala/scala-seed.g8.

You can also run brew edit giter8, delete the disable! because: "fetches unversioned dependencies at runtime" line and rerun brew install giter8, as described here.

@xuwei-k - do you want to get this back in homebrew or should we just encourage users to use the sbt new command?

@benhutchison
Copy link
Contributor

Does sbt new support local testing of templates? That's useful when developing them.

@eed3si9n
Copy link
Member

@danielRicardo
Copy link

danielRicardo commented Nov 5, 2020

@MrPowers I know many non-Scala developers who use Giter8 to generate templates for all kinds of projects. A python team shouldn't have to install sbt to use Giter8 templates (as long as they're not developing other templates)

@TonioGela
Copy link
Member

TonioGela commented May 30, 2021

Coursier based and "curl based" installation methods were added to the Setup page of documentation and the brew one and conscript one were removed, since they are working methods to install giter8 and as @danielRicardo "asked" they do not depend on having an sbt installation locally.

@TonioGela
Copy link
Member

@eed3si9n Is there the intention to restore the homebrew formula?

@eed3si9n
Copy link
Member

I'm not really interested in trying to convince Homebrew core what they should and shouldn't host. I guess we could make our own tap (?) if there's a huge demand for it?

@TonioGela
Copy link
Member

I think 2 kinds of people might want to install giter8:

  • Scala Developers. But in 95% of cases (sorry Mill, Maven, Seed and Gradle users), they already have an sbt installation locally that can supersede giter8 using sbt new.
  • Non-Scala Developers (like @danielRicardo pointed out) that might want to use giter8 as a standalone templating tool. In this case, my previous answer applies: there's Coursier, and there's the curl method. Both if you're on Mac or not.

Creating a tap will force us to maintain it and keep it aligned to the other 2 methods that ATM depend only on publishing CI (so they're more "live" than a homebrew tap). I do agree that the need for a tap depends on the demand but maybe in the meantime we can submit a PR to Homebrew to change the message from Error: giter8 has been disabled! to something like Error: giter8 has been disabled, please refer to the Setup page http://www.foundweekends.org/giter8/setup.html for alternative installation methods?

@TonioGela
Copy link
Member

I've opened this PR to change the error message to

Error: giter8 has been disabled because it fetches unversioned dependencies at runtime.
Please refer to the setup page http://www.foundweekends.org/giter8/setup.html for alternative installation methods!

when someone tries to install giter8 from brew.
If it gets accepted I propose to close this issue since there are alternative installation methods as said before.

@TonioGela
Copy link
Member

Homebrew maintainers closed the issue without much discussion here. IMHO we might consider asking for the removal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

7 participants