You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think bootstrap_ubuntu.sh can simply use UPDATE.sh -s, which would be simpler.
The difference would be that UPDATE.sh -s runs `configure_gnome.sh. I'm not sure why it does that though. It looks a bit dangerous as people who update their VM could be overwriting their gnome settings.
Not urgent of course
The text was updated successfully, but these errors were encountered:
This seems dangerous as it could override user settings.
In addition, it allows us to simplify the bootstrap script a bit.
This also means that INSTALL*sh scripts appropriate to the desired version are used
(before they were the ones on master).
FixesSyneRBI#739
This seems dangerous as it could override user settings.
In addition, it allows us to simplify the bootstrap script a bit.
This also means that INSTALL*sh scripts appropriate to the desired version are used
(before they were the ones on master).
I had to split the optional updates then however, as apt needs to be run
before we can find the python executable. Similarly, python updates have
to be run before we can find cython.
FixesSyneRBI#739
This seems dangerous as it could override user settings.
In addition, it allows us to simplify the bootstrap script a bit.
This also means that INSTALL*sh scripts appropriate to the desired version are used
(before they were the ones on master).
I had to split the optional updates then however, as apt needs to be run
before we can find the python executable. Similarly, python updates have
to be run before we can find cython.
FixesSyneRBI#739
This script contains
SIRF-SuperBuild/VirtualBox/scripts/bootstrap_ubuntu.sh
Lines 74 to 76 in ec4b9c5
As we have
SIRF-SuperBuild/VirtualBox/scripts/UPDATE.sh
Lines 157 to 159 in ec4b9c5
I think
bootstrap_ubuntu.sh
can simply useUPDATE.sh -s
, which would be simpler.The difference would be that
UPDATE.sh -s
runs `configure_gnome.sh. I'm not sure why it does that though. It looks a bit dangerous as people who update their VM could be overwriting their gnome settings.Not urgent of course
The text was updated successfully, but these errors were encountered: