-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
tools: remove rpm build scripts #43647
Conversation
I added these in 2013 but I don't think anyone uses them and I'm not even sure they still produce a working package. I move to remove them because that makes subsequent cleanup a little easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. But I would like to consider that this may explode NodeSource's rpm distributions; would you mind if I reach NodeSource distributions first (before landing this)? AFAIK, lots of people use it to install Node.js; this could potentially affect lots of people
@juanarbol Sure, go ahead. I believe @rvagg once mentioned you don't but that was years ago. |
Thank you @juanarbol for asking us. @bnoordhuis is right, we don't use these files anymore. They can be removed without affecting us. |
Do this needs CI? |
Nope, nothing tests it. |
Landed in 7a0164a |
I added these in 2013 but I don't think anyone uses them and I'm not even sure they still produce a working package. I move to remove them because that makes subsequent cleanup a little easier. PR-URL: #43647 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
I added these in 2013 but I don't think anyone uses them and I'm not even sure they still produce a working package. I move to remove them because that makes subsequent cleanup a little easier. PR-URL: #43647 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
I added these in 2013 but I don't think anyone uses them and I'm not even sure they still produce a working package. I move to remove them because that makes subsequent cleanup a little easier. PR-URL: #43647 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
I added these in 2013 but I don't think anyone uses them and I'm not even sure they still produce a working package. I move to remove them because that makes subsequent cleanup a little easier. PR-URL: nodejs/node#43647 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
I added these in 2013 but I don't think anyone uses them and I'm not
even sure they still produce a working package.
I move to remove them because that makes subsequent cleanup a little
easier.