Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

Nodenv variant #28955

Closed
maxnordlund opened this issue May 4, 2014 · 19 comments
Closed

Nodenv variant #28955

maxnordlund opened this issue May 4, 2014 · 19 comments

Comments

@maxnordlund
Copy link
Contributor

There are two mayor variants of the nodenv script/handler, OiNutters and wfarrs. Currently the wafarr variant is in homebrew, see #28830. This is also the variant used by Boxen. However, it hasn't been updated in a year, unlike OiNutter who updated 13 days ago at the time of this writing.

I believe both should be in homebrew, but the OiNutters variant being the default since it's actively being worked upon. Perhaps wfarrs variant could be renamed to something like nodenv-boxen or boxen-nodev. Another possiblility is to put it in homebrew-versions. Either way, it'll be good to have a discussion about this so future people wondering why X was chosen over Y knows the reasons.

@adamv
Copy link
Contributor

adamv commented May 4, 2014

Any chance OiNutters and wfarrs can fight it out, and one of them can rename their project?

@maxnordlund
Copy link
Contributor Author

Ping @OiNutter and @wfarr, how do you want to handle this?

@OiNutter
Copy link

I don't mind what the general consensus is, obviously I'd prefer not to change mine. I think the main advantage potentially for people using @wfarr's version over mine is that the install and uninstall commands are included with it, whereas mine requires the node-build plugin, as per the structure of rbenv. I haven't however done much change to deal with potential problems with installing on different environments, all the installs I've tried have "just worked" so I've not seen any need and not had any reported issues with installs.

@terryp
Copy link

terryp commented Jun 12, 2014

I spent a couple of hours last night bootstrapping a new Mac. And it didn't occur to me that there could be two libraries with the same names. And yet, there are. I second @maxnordlund suggestion that the lib that is actively maintained be changed in the brew repo. I just looked at @wfarr's contributions recently and it seems very Go-centric. I know I can just change my own formula, but this double dip is a bit confusing - maybe only to me.

@wfarr
Copy link
Contributor

wfarr commented Jun 12, 2014

I'm fine with this change, personally.

@OiNutter Does the node-build plugin support downloading precompiled binaries? If not, I think this would be a great thing to support, because there's really not any sense for most folks to compile full versions of node. If your software has this functionality, I'm more than happy to update the README on mine to consider it deprecated in favor of yours.

@OiNutter
Copy link

@wfarr I don't think so, like I said I've pretty much just copied rbenv, changed the ruby references to node and stripped out the stuff I obviously wasn't going to need (jRuby type stuff). I can have a look at adding that in though.

@jacknagel
Copy link
Contributor

Will review a pull request to make the appropriate change once a solution is agreed upon among the affected projects.

@henriksjostrom
Copy link

@OiNutter and @wfarr
Perhaps you could resolve this conflict?

@OiNutter
Copy link

I think the current state of affairs is I need to test mine works with precompiled binaries. I just haven't had much free time of late to take a look at it.

@ianks
Copy link

ianks commented Sep 10, 2014

I noticed https://github.com/wfarr/nodenv hasn't been updated in a year so I figured it would be best to keep a maintained version on Homebrew. As a user, I would much prefer using @OiNutter's maintained version.

That being said, I pull requested @OiNutter's version here and things seem to be looking well. Will you guys take a look? #32193

Cheers!

@jasonkarns
Copy link
Contributor

I'm fine with this change, personally.

It appears that both @wfarr and @OiNutter are okay with this change? (to make @OiNutter 's variant the default and give @wfarr 's variant a different name). I realize that everyone involved would like to see @OiNutter 's variant be updated to support precompiled binaries. However, I don't think precompiled-binaries shouldn't be a blocker for moving forward with the rename/change-default-formula. Granted, it's slightly annoying that each install of node now requires a full compile, but I think it's more harmful to the homebrew/nodenv community that the name confusion continue for much longer.

I would like to see the rename occur ASAP and let work continue in parallel for adding precompiled-binary support to @OiNutter 's variant. There is already a nodenv/node-build#11 for getting precompiled binary support into node-build.

@MikeMcQuaid
Copy link
Member

It appears that both @wfarr and @OiNutter are okay with this change?

Sorry, I'm maybe being stupid but is there a citation for wfarr saying this somewhere?

@jasonkarns
Copy link
Contributor

@MikeMcQuaid #28955 (comment)

I'm fine with this change, personally.

@icopp
Copy link

icopp commented Sep 8, 2015

It sounds like there's consensus from both project owners about this - so should the change be made, then?

@MikeMcQuaid MikeMcQuaid reopened this Sep 9, 2015
@MikeMcQuaid
Copy link
Member

Yes, I'm OK with this. Can someone open a PR? Thanks!

@jasonkarns
Copy link
Contributor

I can open a PR to swap @wfarr 's version with @OiNutter's. But what should happen to @wfarr's version? Renamed? Moved to one of the homebrew taps?

(And per @wfarr 's concern above, we have just deployed binary-installation support!)

@MikeMcQuaid
Copy link
Member

@jasonkarns It can be left as-is; it's fine for us to just change the version. If you can open a PR that'd be good.

@jasonkarns
Copy link
Contributor

@MikeMcQuaid pr here #45578

nodenv formula also has a recommended dependency on node-build, which is added with #45576

@jasonkarns
Copy link
Contributor

This can be closed now (by #45576)

@Homebrew Homebrew locked and limited conversation to collaborators Jul 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests