Closed paskino closed 4 years ago
What about creating a symbolic link? SyneRBI_VM -> CCPPETMR_VM
Needs repo changes in bootstrap_ubuntu.sh
and possibly other files
What about creating a symbolic link? SyneRBI_VM -> CCPPETMR_VM
good idea, if CCPPETMR_VM exists and SyneRBI_VM doesn't, create the link
update.sh
needs to use ~/devel/SyneRBI_VM
. Probably other things as well.
What about creating a symbolic link? SyneRBI_VM -> CCPPETMR_VM
good idea, if CCPPETMR_VM exists and SyneRBI_VM doesn't, create the link
I'm thinking that this is going to complicate the things in a consistent way for no real reason. The important bit is to update the github links (though not fundamental either).
Wouldn't it be better to create a new VM? We may then release it with SIRF as 2.1.x.
I'm thinking that this is going to complicate the things in a consistent way for no real reason.
You mean creating the CCPPETMR_VM
link? Or change update.sh
? Things have to work, both for a new one and for updating an existing (but not too old) one. Not everyone is using their VMs for a short time (otherwise, why do we have the update mechanism at all?).
Wouldn't it be better to create a new VM? We may then release it with SIRF as 2.1.x.
Agreed that it would be best to create a new VM, but it seems hard to do it without a new release. how are we going to call it otherwise?
created a VM from scratch with this branch and it works. I'll try to upload it somewhere for test.
created a VM from scratch with this branch and it works. I'll try to upload it somewhere for test.
This looks ok to me now. However, I did spot a problem with the automatic set remote
. On my VM, I had changed the remote manually to something else (actually git@github.com:...
such that I don't need to type passwords all the time). Doing on update_VM.sh
got rid of all these.
As the ccppetmr redirects are all working fine, I suggest that we remove these. People with old VMs will have no problems. People with new VMs will get the synerbi repo.
Objections? @casperdcl @paskino
I've introduced an option for the remote. Also changed the "version" stuff a bit.
we probably need to manage that an old VM will have files in
~/devel/CCPPETMR_VM
which will now have been changed.This most likely also affects this wiki