#11676: sage-pkg does not force world-readable permissions
-------------------------------+--------------------------------------------
   Reporter:  AlexanderDreyer  |          Owner:  AlexanderDreyer               
       Type:  enhancement      |         Status:  needs_info                    
   Priority:  major            |      Milestone:  sage-duplicate/invalid/wontfix
  Component:  scripts          |       Keywords:  chmod umask install mode      
Work_issues:                   |       Upstream:  N/A                           
   Reviewer:                   |         Author:  Alexander Dreyer              
     Merged:                   |   Dependencies:                                
-------------------------------+--------------------------------------------

Comment(by leif):

 Replying to [comment:30 AlexanderDreyer]:
 > Replying to [comment:29 leif]:
 > > The added spkg "sanity check" regarding permissions is IMHO
 superfluous and rather annoying; as Keshav mentioned, we should in general
 leave the upstream alone, i.e., ship it really vanilla, and maybe fix
 individual permissions in the corresponding `spkg-install` file if
 necessary.
 > I don't agree (it would have helped to avoid #11664), but it seems
 there's no way to fix the ticket.

 I didn't mean `sage -pkg` (i.e., a sanity check regarding permissions
 ''there'', although you'd have the same problems unless you're upstream),
 but the ''merger script'' which complains about any "suspicious"
 permissions since -- as mentioned -- it's hard or impossible to do a
 ''reasonable'' check regarding this, i.e., to make sure all ''installed
 files'' have or will have the correct permissions.

 So I wouldn't mind if `sage -pkg` issued warnings (to perhaps be disabled
 by some option), but the proper or safest way to avoid such issues is IMHO
 still to set the umask and do a `chmod -R` on `src/` at least (from `sage-
 spkg`), although this will in most cases be redundant or superfluous (e.g.
 if `install -c -m ...` is used by the spkg anyway, or all files to be
 copied with `cp -p` already have the proper permissions).  In fact, a
 sanity check should be made ''on the Sage installation'', after one or
 more (or all) spkgs have been built and installed.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11676#comment:31>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to