On 05/ 6/11 10:08 AM, Jeroen Demeyer wrote:
On 2011-05-05 23:42, Dr. David Kirkby wrote:
I've often wondered if it would be possible to safely remove the write
permissions from the "src" directory and everything below it, so files
can't be accidentally changed.
I believe that would reduce the chances of the "src" being corrupted.
Just wondering, is this an actual problem? Does *accidental* corruption
of src/ happen sufficiently often that we need to do something about this?
I can imagine something going wrong when src/ is updated to a new
upstream version, but permissions are not going to help that situation.
At that point, src/ is writable.
Jeroen.
There have been a number of packages to which the contents under "src" have been
purposely made by people not knowing what they are doing. I've lost count of them.
Only a week or two ago (during the 4.7 release), there was a file which got
patched in "src" when "patch" was run from spkg-install. It was related to
building Python on some Linux version - I forget the ticket.
I suspect with the increased use of "patch" and less use of "cp" when applying
patches, it will become easier to make a mistaken and patch the upstream source
by mistake.
So, it it was possible to protect against that, I think it would be a good idea.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
