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

Distribution via package managers #5

Open
EivindArvesen opened this issue Sep 19, 2015 · 12 comments
Open

Distribution via package managers #5

EivindArvesen opened this issue Sep 19, 2015 · 12 comments

Comments

@EivindArvesen
Copy link
Owner

prm should be distributed through various package managers (e.g. apt, brew, macports, pacman, yum...), though it should perhaps be postponed until there is a stable release.

Needs to include an append (alias) to a user dotfile or at least a message regarding proper use of prm (i.e. sourcing the script), e.g. via a post-install hook.

@EivindArvesen EivindArvesen changed the title Package manager distribution Distribution via package managers Sep 19, 2015
@EivindArvesen EivindArvesen added this to the 1.0.0 milestone Sep 19, 2015
@bogas04
Copy link

bogas04 commented Sep 19, 2015

npm as well!

@EivindArvesen
Copy link
Owner Author

npm is a package manager specifically for JavaScript modules (e.g. for use with Node.js), though.

I'm talking about OS package managers, like Homebrew for Mac OS X, and those that come bundled with various Linux distros (e.g. apt with Debian and Ubuntu).

@bogas04
Copy link

bogas04 commented Sep 20, 2015

Yeah it makes sense however having it on npm would make it easy to install on any OS.
I do realize it doesn't really fall under this issue, but I see npm also as a multi-platform package manager.

Maybe later at some point we can parse the sh files and provide a node module for the same too.

require('prm').projects.map((p) => console.log(p));

@EivindArvesen
Copy link
Owner Author

I understand what you mean, but that's not what npm is or is for, as far as I understand.

I just don't see a point in distributing prm via a JavaScript package manager when it is not written in JavaScript, and when prm has no place in the JavaScript ecosystem.

On the other hand, if there were a js-binding (and supposably a need for npm's functionality in js/Node), it could be distributed via npm, with this repo as a dependency.

@bogas04
Copy link

bogas04 commented Sep 20, 2015

Cool, makes sense !

@bogas04
Copy link

bogas04 commented Sep 22, 2015

Hey!
I implemented prm using NodeJS coz it looked like a fun exercise! I have mentioned about your project in credits.

You can have a look at it here

screen shot 2015-09-22 at 8 19 30 pm

@EivindArvesen
Copy link
Owner Author

@bogas04: While I appreciate your effort, I would like for you not to use the prm name in your project.

This is because, unlike @FredDeschenes' prm-fish, your project is not a port of prm, is not API-compatible, and doesn't perform the same tasks as prm does.

Since your software is very different from prm, this is likely to be very confusing for users.
Please tell me if you disagree with my reasoning, and if so, why.

I'd also appreciate if anyone else would like to chime in here.

@bogas04
Copy link

bogas04 commented Sep 22, 2015

Sure, no problem! Off to thinking for name

@EivindArvesen
Copy link
Owner Author

Great! Good luck with your project:)

@bogas04
Copy link

bogas04 commented Sep 22, 2015

Thank you for being so supportive ! :)

@bogas04
Copy link

bogas04 commented Sep 22, 2015

Renamed @eivind88 :) npm i node-pmc -g

@EivindArvesen
Copy link
Owner Author

#4 might be relevant.

@EivindArvesen EivindArvesen modified the milestone: 1.0.0 Oct 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants