Ticket #1444 (closed defect: fixed)
[with patch] some serious hard-coding issues that break all binary installs
| Reported by: | was | Owned by: | mabshoff |
|---|---|---|---|
| Priority: | blocker | Milestone: | sage-2.9 |
| Component: | distribution | Keywords: | |
| Cc: | Author(s): | ||
| Report Upstream: | Reviewer(s): | ||
| Merged in: | Work issues: |
Description
Hi,
There are a few very serious (but easy to fix)
problems with the current sage and upcoming packages
that involving hardcoding of paths. These
will cause problems if you move a sage install.
POLYBORI:
I noticed this in a SAGE_ROOT/local/bin/:
lrwxr-xr-x 1 was was 47 Dec 4 10:52 ipbori -> /Users/was/s/local/share/polybori/ipbori/ipbori
That link *must* not be hard coded. Make sure this gets fixed before polybori is in sage.
SINGULAR (very serious):
Several Singular-related files in SAGE_ROOT/local/bin/ have hardcoded paths.
This makes it so singular will fail to work for everybody who downloads a sage
binary right now :-(.
The package singular-3-0-4-1-20071209.spkg fixes the problem. Just do
sage -upgrade to get it, or download it from
http://sagemath.org/packages/standard/singular-3-0-4-1-20071209.spkg
BZIP2:
Some minor path hardcoding problems. Easy to fix. I've put the file that needs
to be replaced here...
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

