Use a symbolic link instead of copy to /usr/local/sbin/.. #165

New Issue

2023-10-04T20:30:39+02:00

A-Fromell-ITxPT commented

2023-10-04 20:30:39 +02:00

(Migrated from github.com)

I propose to use symbolic links for the cloned files instead of copy them to /usr/local/sbin
Ex.
sudo ln -s $(pwd)/rpi-clone /usr/local/sbin/rpi-clone
sudo ln -s $(pwd)/rpi-clone-setup /usr/local/sbin/rpi-clone-setup

The major advantage is:
if you update to the latest release by:
sudo git fetch https://github.com/billw2/rpi-clone.git

If/when updates are made to rpi-clone or rpi-clone-setup the links in /usr/local/sbin are then pointing to the new updated files.
Eg. no need to copy the files..

Best regards,
Anders Fromell

I propose to use symbolic links for the cloned files instead of copy them to /usr/local/sbin Ex. sudo ln -s $(pwd)/rpi-clone /usr/local/sbin/rpi-clone sudo ln -s $(pwd)/rpi-clone-setup /usr/local/sbin/rpi-clone-setup The major advantage is: if you update to the latest release by: sudo git fetch https://github.com/billw2/rpi-clone.git If/when updates are made to rpi-clone or rpi-clone-setup the links in /usr/local/sbin are then pointing to the new updated files. Eg. no need to copy the files.. Best regards, Anders Fromell

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Lerking/rpi-clone#165