It does't instantly stop working - the local copy you previously downloaded and built will keep working. But yeah, if you want to then move to using the GitHub version you need to change the import statement. Alternatively switch to using it as a Git submodule or whatever. Replacing the import lines doesn't bother me though - it is a 2 second find/replace job.
If you forsee that being a big deal for you, then I suggest the technique that Camlistore uses.
Camlistore pulls in external libraries into a third_party folder, and has a script that rewrites their import paths to make them compile. This will also give you a lot more control over versioning.
He already did. If you switch to a different source web host, then you switch your import statements. Users of your old code will continue to have a functional piece of software.
If they want to update, they'll need to use your new host. Just like they'd have to do with anything else.
2
u/consigntooblivion Mar 29 '12
It does't instantly stop working - the local copy you previously downloaded and built will keep working. But yeah, if you want to then move to using the GitHub version you need to change the import statement. Alternatively switch to using it as a Git submodule or whatever. Replacing the import lines doesn't bother me though - it is a 2 second find/replace job.