#9896: Upgrading from 4.5.3 to 4.6.alpha* can fail (not limited to MacOS X)
------------------------------+---------------------------------------------
   Reporter:  jhpalmieri      |       Owner:  GeorgSWeber                       
      
       Type:  defect          |      Status:  needs_review                      
      
   Priority:  blocker         |   Milestone:  sage-4.6                          
      
  Component:  build           |    Keywords:  upgrade update dependencies PARI 
NewPARI
     Author:  Leif Leonhardy  |    Upstream:  N/A                               
      
   Reviewer:                  |      Merged:                                    
      
Work_issues:                  |  
------------------------------+---------------------------------------------

Comment(by leif):

 Replying to [comment:100 jdemeyer]:
 > Replying to [comment:94 leif]:
 > > Well, {{{spkg/install}}} and {{{spkg/standard/deps}}} are current
 again, but you've checked the (also current) {{{install}}} in (s.t. it's
 now in the Sage scripts repo, and also ends up in
 {{{$SAGE_ROOT/local/bin}}} where the scripts repo of the installation
 lives):
 >
 > But why is it copied to {{{$SAGE_ROOT/local/bin}}}? Surely, putting the
 file under revision control should not have that as consequence?

 {{{sage_scripts-*.spkg}}} ''contains'' the {{{local/bin/.hg}}} repository
 (at the ''top'' level), and '''only''' that. If during installation of the
 spkg a repository already exists in {{{$SAGE_LOCAL/bin}}}, it gets
 synchronized from that, so any file checked into the spkg's repo will be
 "copied" to {{{$SAGE_LOCAL/bin}}}. Other files in the spkg's top-level
 directory (i.e., in {{{.hgignore}}}) won't.

 It would perhaps be less confusing if that spkg had the same structure as
 almost all others, i.e. the files ''to be installed'' in {{{src/}}}
 (including the {{{local/bin}}} repo), and the files that ''manage the
 installation'' in the top-level directory, {{{sage_scripts-*/}}}, along
 with their '''own''', separate, Mercurial repository.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9896#comment:101>
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