Do not install to /usr/bin but to /usr/local/bin or /opt/bin #75

Closed
autostatic opened this Issue Mar 1, 2013 · 10 comments

Comments

Projects
None yet
4 participants

Maybe it's better to install the rpi-update script to /usr/local/bin or /opt/rpi-update/bin. This way it will never get overwritten by the contents of any package that might contain a script or binary that is also called rpi-update.

Jeremy

K1773R commented Mar 1, 2013

dpkg wont overwrite anything, it will error out. still ur right, script/binary should be in /usr/local/bin

Oops, you're right, dpkg won't do that.

Maybe $HOME/bin is even better.

K1773R commented Mar 4, 2013

bad idea for a multi user system.

I don't see why unless all users have sudo rights.

K1773R commented Mar 5, 2013

then everyone would have to put it into ~/bin and enlarge $PATH in ~/.bashrc
if you put it in /usr/local/bin everyone can use it.

Check $HOME/.profile, it's already there.

K1773R commented Mar 5, 2013

i dont have my rpi with raspbian with me so i cant check that, altough the other argument (about the need of installing it per user) still exist

$HOME/bin isn't such a good idea because root has a different $PATH env than a normal user. Same goes for /opt/rpi-update/bin but that is easier to set system-wide.

Contributor

lurch commented Sep 1, 2013

There's nothing in the script itself that forces it to be in /usr/bin - if you want to put it in a different directory such as /usr/local/bin or $HOME/bin you're free to do so. And there's nothing that means it has to be in the default search $PATH either.

And now that rpi-update has been packaged (and included by default) in Raspbian (see #93), maybe this bug should be closed?

popcornmix closed this Apr 5, 2014

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