Make a "release" directory in the sagenb repo that generates a new proper sagenb spkg
The top level of the sagenb spkg does not have an hg repository, which is very confusing since all spkg's are supposed to. It turns out that spkginstall is autogenerated and SPKG.txt is in sagenb's own repository, i.e., in sagenb0.9.0/src/sagenb/SPKG.txt
.
Jason Grout and William Stein discussed this for a while and propose the following plan:
 Create a directory
sagenb0.9.0/src/sagenb/release/sage
 Put spkgdist, SPKG.txt there, along with a small hg repo that contains SPKG.txt and spkginstall.
 Use this new spkgdist script to generate a proper sagenb spkg in the usual way. However, it will copy over the hg repo created in 2, then check in spkginstall and SPKG.txt.
The motivation for this is so that the sagenb spkg is the same as the other ones, which could be important for automated tools that make a directory of spkg's, etc.
Change History (7)
Milestone: 
sage5.11 →
sage5.12

Milestone: 
sage6.1 →
sage6.2

Milestone: 
sage6.2 →
sage6.3

Milestone: 
sage6.3 →
sage6.4

Milestone: 
sage6.4 →
sageduplicate/invalid/wontfix

Reviewers: 
→ Jeroen Demeyer

Status: 
new →
needs_review

Status: 
needs_review →
positive_review

Resolution: 
→ fixed

Status: 
positive_review →
closed

Obsolete.