Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Two sage-location related tickets need review
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jeroen Demeyer  
View profile  
 More options Sep 16 2012, 2:54 pm
From: Jeroen Demeyer <jdeme...@cage.ugent.be>
Date: Sun, 16 Sep 2012 20:54:40 +0200
Local: Sun, Sep 16 2012 2:54 pm
Subject: Two sage-location related tickets need review
#13452: Refactor sage-location
Some various clean-up of sage-location, in particular:
   1. Don't use realpath() or abspath() everywhere. Just once should be
more than sufficient.
   2. Merge initialize_pkgconfig_files() and update_pkgconfig_files().
   3. Improve the logic, i.e. install_moved() should not write the
processor flags.
   4. Improve structure by creating a new top-level function
sage_relocate() which then calls the other functions.
   5. Better documentation.

#13407: Move sage-make_relative to sage-location
There is a rare race condition associated to sage-make_relative: when a
file is open for writing, it cannot be executed (you get a "Text file
busy" error). Since the sage-make_relative Python script opens all files
in $SAGE_LOCAL/bin for writing, it can happen that a Sage build fails.
The best solution is to move sage-make_relative to sage-location: the
latter script is intented precisely to fix relocation issues. It would
also be faster, as currently every file in $SAGE_LOCAL/bin is checked
after every package is installed.

Both these tickets are prerequisites for #5155 (Fix doctests that want
write access to $SAGE_ROOT).  I think it would be good to finally fix
this issue, such that Sage works 100% (not 99%) for other users (not the
one who installed Sage).  I would like a push to get this into sage-5.4.

So please review:
http://trac.sagemath.org/sage_trac/ticket/13452
http://trac.sagemath.org/sage_trac/ticket/13407

Thanks,
Jeroen.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeroen Demeyer  
View profile  
 More options Nov 12 2012, 3:06 am
From: Jeroen Demeyer <jdeme...@cage.ugent.be>
Date: Mon, 12 Nov 2012 09:06:03 +0100
Local: Mon, Nov 12 2012 3:06 am
Subject: Re: [sage-devel] Two sage-location related tickets need review
These two tickets still need review:

On 2012-09-16 20:54, Jeroen Demeyer wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »