#11676: sage-pkg does not force world-readable permissions
-------------------------------+--------------------------------------------
Reporter: AlexanderDreyer | Owner: AlexanderDreyer
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: scripts | Keywords: chmod umask install mode
Work_issues: | Upstream: N/A
Reviewer: | Author: Alexander Dreyer
Merged: | Dependencies:
-------------------------------+--------------------------------------------
Comment(by kini):
I agree. Certainly `sage-spkg` should not touch the `src/` directory under
any circumstances, IMO, as the SPKG format should be flexible enough to be
distributed sans the `src/` directory with the expectation that a
particular upstream source archive can be extracted into `src/` before
running `spkg-install` (if we at some point decide to build a more complex
package manager, etc.).
I don't think that changes to the other files in the SPKG should be made
by `sage-spkg` immediately before archiving, either, because this results
in uncommitted changes in the Mercurial repository shipped inside the
SPKG, which is not good. Though I guess you may disagree with me on this
point, Jeroen, as (IIRC) you use scripts which make automated commits in
SPKGs before publishing them, right?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11676#comment:21>
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.
