Opened 15 years ago

Closed 14 years ago

#141 closed defect (wontfix)

sage -ldist -- needs to be updated

Reported by: was Owned by: was
Priority: major Milestone:
Component: packages: standard Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

On Fri, 20 Oct 2006 18:06:42 -0700, Mark <mfenner@…> wrote:

Could someone provide a basic road map of what would need to be done to separate the interfaces (i.e., Python code) from the batteries included distribution? Aside from extracting sage-<version> from spkg/sage-<version> and doing python setup.py install, that is ...

First, something that might be helpful is to try typing

"sage -ldist VER"

which ends up running

<SAGE_ROOT>/local/bin/sage-libdist

which is supposed to make a "stand alone" version of SAGE without dependencies. I.e., a tarball that you can "python setup.py install" into a standard Python2.5 install, assuming you have all dependencies.

It is "slightly" behind, i.e,. I haven't used it in months, so it is not likely to work. But it is a first step in the direction of what you want.

[...]

I just tried "sage -ldist" and it failed because it isn't aware of how I reorganized where the custom ipython config files go; basically, it fails in creating an ipython config for SAGE. But it gets close -- in particular, if you run it you'll get a directory

<SAGE_ROOT>/dist/sage-....

that has a setup.py file in it.

I haven't kept it up only because the user base until now has not actually requested it. I'll list that "sage -ldist" doesn't quite work as a bug on the tracker, so I can fix it soon.

Change History (1)

comment:1 Changed 14 years ago by was

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.