Opened 12 years ago

Closed 11 years ago

#5296 closed defect (duplicate)

[with file] Update the OS X Readme

Reported by: GeorgSWeber Owned by: iandrus
Priority: minor Milestone: sage-duplicate/invalid/wontfix
Component: distribution Keywords:
Cc: mabshoff Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

With the switch to an app bundle distribution for Mac OS X, the file "$SAGE_ROOT/sage-README-osx.txt" contains obsolete parts (the "steps 4 - 6", and the last lines right at the end).

A -bdist'ed OS X .dmg contains another README.txt file of the same outdated content, probably it is just the first one copied during creation of the .dmg.

Attachments (2)

sage-README-osx.txt (849 bytes) - added by kcrisman 12 years ago.
sage-README-osx.2.txt (1.7 KB) - added by iandrus 11 years ago.

Download all attachments as: .zip

Change History (17)

comment:1 Changed 12 years ago by mabshoff

  • Milestone changed from sage-3.4 to sage-3.4.1

Better luck in 3.4.1.

Cheers,

Michael

Changed 12 years ago by kcrisman

comment:2 Changed 12 years ago by kcrisman

  • Priority changed from critical to minor
  • Summary changed from Update the OS X Readme to [with file] Update the OS X Readme

I don't know how to check whether this "works", but at any rate once Sage is automatically distributed in the app bundle, this should go in.

I'm also changing priority, since no one has complained in half a year.

comment:3 Changed 12 years ago by GeorgSWeber

I'm fine with changing the priority. As far as I remember, Michael Abshoff asked me to create this ticket. Unfortunately, nobody seems to want to work on "app-ifying" Sage on OS X since his leave.

comment:4 Changed 11 years ago by iandrus

  • Owner changed from mabshoff to iandrus
  • Report Upstream set to N/A

Now that I hopefully have a little more time I plan to work on "app-ifying" Sage. What is preventing us from distributing sage in the app bundle automatically? Is there a reason we don't just make SAGE_APP_BUNDLE=yes the default?

comment:5 Changed 11 years ago by kcrisman

Apparently there were some movement issues, that is to say moving the Sage installation within the computer didn't always work properly. There is an open ticket about this, #5254. #5261 is also related. I like #7546, too - can't review it in detail now, but it would be great to finally get this taken care of, and I would be happy to help out with reviewing duties once I'm in a position to do so.

comment:6 Changed 11 years ago by kcrisman

Now that #5254, #5261, and #7546 are more or less resolved, we should resolve this situation. Note that sage-bdist doesn't currently automatically make an app bundle yet, and this should probably be resolved on sage-devel, for the following reason: some people, perhaps many, will want to have both the notebook and command line options, but the current script makes the notebook only. We should definitely eventually distribute a notebook-only one, but I'm not sure that should be the default until we have both available. Ideally, this would be yet another environment variable for sage-bdist :)

But we're very, very close! So much thanks to iandrus for making huge leaps over my initial small steps on all this.

Changed 11 years ago by iandrus

comment:7 Changed 11 years ago by iandrus

  • Status changed from needs_work to needs_review

I'm not sure I made the readme any simpler, but at least it should be accurate once we start distributing the sage application.

comment:8 Changed 11 years ago by jhpalmieri

See also #6938.

comment:9 Changed 11 years ago by kcrisman

This looks fine to me. Positive review if we ever actually distribute these.

What we really need to do is distribute the notebook binary and also just a regular (perhaps non-bundle) binary, but maybe this is a lot to host when it comes to mirrors?

Or, again, figure out how to make the app bundle let you choose between command line and notebook.

comment:10 Changed 11 years ago by kcrisman

With respect to #6938, be sure to only do this with the copy in /local/bin . The other one should probably be removed.

comment:11 Changed 11 years ago by kcrisman

#9873 is related, and may eventually supersede this.

comment:12 follow-up: Changed 11 years ago by mpatel

  • Status changed from needs_review to positive_review

Release manager

Please close this ticket as a "duplicate" when #9873 is merged.

comment:13 in reply to: ↑ 12 ; follow-up: Changed 11 years ago by kcrisman

Replying to mpatel:

Release manager

Please close this ticket as a "duplicate" when #9873 is merged.

Or, 'merge' this one first and then #9873 (as noted in that ticket's comments).

comment:14 in reply to: ↑ 13 Changed 11 years ago by kcrisman

Replying to kcrisman:

Replying to mpatel:

Release manager

Please close this ticket as a "duplicate" when #9873 is merged.

Or, 'merge' this one first and then #9873 (as noted in that ticket's comments).

Sorry for the noise - jhpalmieri is right in his comments in #9873. Treat as previously mentioned.

comment:15 Changed 11 years ago by mpatel

  • Milestone changed from sage-4.6 to sage-duplicate/invalid/wontfix
  • Resolution set to duplicate
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.