The location string is a deployer assigned persistent identifier, so it cannot change. Your confusion arises because frameworks use the URL as the default location string for simple installs, but the two are unrelated in reality.
Matias SM <[email protected]> wrote: >Ok, I see. Shouldn't the location string be replaced (with the updated >version location) when the bundle is updated? It seems a little >confusing. > >Thank you very much for the clarification, I will do some more >experimentation keeping in mind what we discussed. > >On 02/04/12 19:25, Richard S. Hall wrote: >> Yes, you are using the same path when you try to install the first >bundle the second time and this will not work since that path is used >as a unique key, which is why it returns the same bundle id as printed >in your session since it did not install anything the second time. >> >> As I suggest you need to have two different paths. >> >> However, this isn't an issue for OBR since it uses an arbitrary >location string, so it is always unique when it does an install, which >you can't easily do from the shell, like I said before. >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] -- Sent from my phone, excuse my brevity.
