Hi all, after a lot of confusion I discovered that first-setup.sh is not Andy-proof. If there is a broken internet connection, the update lua process works and pushes the rsync error message very quickly out of the terminal. I propose to change the rsync line to rsync -rlptv rsync://contextgarden.net/minimals/setup/$platform/bin . || { echo "Cannot reach the repository"; exit 1; } Andy P.S. Someone already did the same to the ruby error message, it is copied a second time at the end.
On Fri, Jun 8, 2012 at 6:40 PM, Andy Thomas wrote:
Hi all,
after a lot of confusion I discovered that first-setup.sh is not Andy-proof. If there is a broken internet connection, the update lua process works and pushes the rsync error message very quickly out of the terminal. I propose to change the rsync line to
rsync -rlptv rsync://contextgarden.net/minimals/setup/$platform/bin . || { echo "Cannot reach the repository"; exit 1; }
Thank you, that makes sense, I'll change it. But I believe that some similar safeguards might be needed in the lua script (there is a slight chance that this would go through and the calls in lua script wouldn't). Mojca
On Fri, Jun 8, 2012 at 6:47 PM, Mojca Miklavec wrote:
On Fri, Jun 8, 2012 at 6:40 PM, Andy Thomas wrote:
Hi all,
after a lot of confusion I discovered that first-setup.sh is not Andy-proof. If there is a broken internet connection, the update lua process works and pushes the rsync error message very quickly out of the terminal. I propose to change the rsync line to
rsync -rlptv rsync://contextgarden.net/minimals/setup/$platform/bin . || { echo "Cannot reach the repository"; exit 1; }
Thank you, that makes sense, I'll change it.
But I believe that some similar safeguards might be needed in the lua script (there is a slight chance that this would go through and the calls in lua script wouldn't).
Also, if the file doesn't exist on the server (if you change a letter in path or if platform would be removed from supported one for example), it doesn't stop. I didn't try to investigate if there is an easy way around that. Also keep in mind that users need to update the original script (currently still called first-setup.sh) manually. Mojca
On Fri, 8 Jun 2012, Mojca Miklavec wrote:
Also keep in mind that users need to update the original script (currently still called first-setup.sh) manually.
FWIW, I updated the PKGBUILD for arch linux: https://aur.archlinux.org/packages.php?ID=30398 Aditya
On 8-6-2012 18:54, Mojca Miklavec wrote:
On Fri, Jun 8, 2012 at 6:47 PM, Mojca Miklavec wrote:
On Fri, Jun 8, 2012 at 6:40 PM, Andy Thomas wrote:
Hi all,
after a lot of confusion I discovered that first-setup.sh is not Andy-proof. If there is a broken internet connection, the update lua process works and pushes the rsync error message very quickly out of the terminal. I propose to change the rsync line to
rsync -rlptv rsync://contextgarden.net/minimals/setup/$platform/bin . || { echo "Cannot reach the repository"; exit 1; }
Thank you, that makes sense, I'll change it.
But I believe that some similar safeguards might be needed in the lua script (there is a slight chance that this would go through and the calls in lua script wouldn't).
Also, if the file doesn't exist on the server (if you change a letter in path or if platform would be removed from supported one for example), it doesn't stop. I didn't try to investigate if there is an easy way around that.
Also keep in mind that users need to update the original script (currently still called first-setup.sh) manually.
Maybe this is then the right time to do the renaming: fetch-context or so, as an update is not a first Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (4)
-
Aditya Mahajan -
Andy Thomas -
Hans Hagen -
Mojca Miklavec