Skip to content

Make cargo repo compatible with homebrew formulae #808

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

Closed
pnkfelix opened this issue Nov 6, 2014 · 19 comments · Fixed by #995 or #1531
Closed

Make cargo repo compatible with homebrew formulae #808

pnkfelix opened this issue Nov 6, 2014 · 19 comments · Fixed by #995 or #1531

Comments

@pnkfelix
Copy link
Member

pnkfelix commented Nov 6, 2014

A colleague is interested in trying to help write a homebrew formula for installing cargo, so that brew install cargo will work.

One hurdle that my colleague pointed out is that the homebrew policies for acceptable formulae requires that stable versions be tagged in the upstream project repository. I'm not a cargo developer, so perhaps the plan is indeed to start using the tag mechanism once we have hit a version beyond 0.0.1-pre, but we have not yet hit a stable version, and thus no tags yet exist.

Anyway, I figured I would open this ticket to track any effort towards homebrew compatibility, with the intention that this ticket be closed once brew install cargo does something plausible. :)

@phrawzty
Copy link

phrawzty commented Nov 6, 2014

A colleague is interested in trying to help write a homebrew formula for installing cargo, so that brew install cargo will work.

For reference, I am the colleague. 🐸 I'm happy to prepare to write the brew formula (etc) and act as a maintainer if the upstream requirements are met.

@alexcrichton
Copy link
Member

I'd love to get this working! Is there anything that the repo needs to do other than have a tag somewhere inside it? I could just make a tag and bump the version number slightly in that case!

@phrawzty
Copy link

phrawzty commented Nov 7, 2014

Once of the requirements for inclusion in the base Homebrew channel is having tagged "stable releases" for the repo in question. For projects that don't have stable releases (i.e. always install HEAD), there is a "headonly" tap; however, this is generally considered bad form, so reliably tagging stable releases would be the best bet.

alexcrichton added a commit to alexcrichton/cargo that referenced this issue Nov 30, 2014
bors added a commit that referenced this issue Nov 30, 2014
@bors bors closed this as completed in #995 Nov 30, 2014
@phrawzty
Copy link

Hi,

I see that this was closed, however, #995 does not fulfil this bug. To be clear, for brew compatibility each stable release must be (git) tagged as appropriate; I note that the cargo tag list contains only 0.0.1-pre.

@schickling
Copy link

+1

@pnkfelix
Copy link
Member Author

it sounds like the fundamental problem here has not been resolved. @alexcrichton please reopen.

@schickling
Copy link

Current workaround:

$ brew cask install cargo

@rogeriopvl
Copy link

+1

@quadrupleslap
Copy link

Has this been done yet? Because brew install cargo still doesn't work afaict.

@pnkfelix
Copy link
Member Author

to my knowledge it is still unaddressed.

@lepture
Copy link

lepture commented Mar 4, 2015

+1

5 similar comments
@bwhitty
Copy link

bwhitty commented Mar 14, 2015

+1

@fiag
Copy link

fiag commented Mar 17, 2015

+1

@pwnall
Copy link

pwnall commented Mar 23, 2015

+1

@nickbroon
Copy link

👍

@iyedb
Copy link

iyedb commented Apr 12, 2015

+1

alexcrichton added a commit to alexcrichton/cargo that referenced this issue Apr 16, 2015
bors added a commit that referenced this issue Apr 16, 2015
@mbaltrusitis
Copy link

+1

@parkr
Copy link
Contributor

parkr commented Apr 28, 2015

still can't brew install cargo. was expecting brew install rust to install cargo as well, but alas.

@archshift
Copy link

brew install rust now installs cargo as of Homebrew/legacy-homebrew@1be7f90

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

Successfully merging a pull request may close this issue.