If a user accidentally modifies a package (for example by using @edit), the package could easily break and I don't think there is a way to detect it.
Perhaps there should be some option of doing an integrity check that checks that the tree hashes in the saved packages actually are what they are supposed to be?
I was imagining a pkg> fsck or pkg> verify command to check all of your dependencies – and maybe fix them for you if they're broken.
Stefan had a thought about making the files read only.
+1 to both read-only and a check (preferably run at each update). I just got bitten by a corrupted file and it took me some time to figure out what is going on.
Would probably need something like https://github.com/simonbyrne/GitX.jl/commit/886bbddfb9d2508b04c6722718967fe558486349 to verify the tree hash.
Would just removing -w on all files work well on all OS?
Discussed at JuliaCon. Making them read-only seems like it gets you 98% of the way there. Right now @edit pkgfoo(x) takes you to this very tempting target for modification...
Most helpful comment
Discussed at JuliaCon. Making them read-only seems like it gets you 98% of the way there. Right now
@edit pkgfoo(x)takes you to this very tempting target for modification...