Revision history [back]
 | 1 | initial version |
When doing a bdist, you only need to provide the Sage version like
sage -bdist 4.6.3
(although you can include more info if you want). The sage-bdist script in $SAGE_ROOT/local/bin/ will automatically prepend sage- and append
`uname -m`-`uname`
So, on my system, doing `
sage -bdist 4.6.3
would produce a file starting with sage-4.6.2-x86_64-Linux.
On OSX, there are some environment variable which will control the type of file that is produced. If SAGE_APP_BUNDLE=yes, then the Sage-4.6.3.app file will be created. If SAGE_APP_DMG != "no" then a .tar.gz file will be created; otherwise a .dmg file will be created.
| | 2 | No.2 Revision |
When doing a bdist, you only need to provide the Sage version like
sage -bdist 4.6.3
(although you can include more info if you want). The sage-bdist script in $SAGE_ROOT/local/bin/ will automatically prepend sage- and append
`uname -m`-`uname`
(edit by kcrisman: which typically give the chip type and OS)
So, on my system, doing `
sage -bdist 4.6.3
would produce a file starting with sage-4.6.2-x86_64-Linux.
On OSX, there are some environment variable which will control the type of file that is produced. If SAGE_APP_BUNDLE=yes, then the Sage-4.6.3.app file will be created. If SAGE_APP_DMG != "no" then a .tar.gz file will be created; otherwise a .dmg file will be created.
| | 3 | No.3 Revision |
Edit: Apparently this was changed in http://trac.sagemath.org/ticket/15527 so now sage -bdist suffices, with an optional temporary directory name. Unclear if that info ever ends up in the
When doing a bdist, you only need to provide the Sage version like
sage -bdist 4.6.3
(although you can include more info if you want). The sage-bdist script in $SAGE_ROOT/local/bin/ will automatically prepend sage- and append
`uname -m`-`uname`
(edit by kcrisman: which typically give the chip type and OS)
So, on my system, doing `
sage -bdist 4.6.3
would produce a file starting with sage-4.6.2-x86_64-Linux.
On OSX, there are some environment variable which will control the type of file that is produced. If SAGE_APP_BUNDLE=yes, then the Sage-4.6.3.app file will be created. If SAGE_APP_DMG != "no" then a .tar.gz file will be created; otherwise a .dmg file will be created.
| | 4 | No.4 Revision |
Edit: Apparently this was changed in http://trac.sagemath.org/ticket/15527 so now sage -bdist suffices, with an optional temporary directory name. Unclear if that info ever ends ended up in the documented.
When doing a bdist, you only need to provide the Sage version like
sage -bdist 4.6.3
(although you can include more info if you want). The sage-bdist script in $SAGE_ROOT/local/bin/ will automatically prepend sage- and append
`uname -m`-`uname`
(edit by kcrisman: which typically give the chip type and OS)
So, on my system, doing `
sage -bdist 4.6.3
would produce a file starting with sage-4.6.2-x86_64-Linux.
On OSX, there are some environment variable which will control the type of file that is produced. If SAGE_APP_BUNDLE=yes, then the Sage-4.6.3.app file will be created. If SAGE_APP_DMG != "no" then a .tar.gz file will be created; otherwise a .dmg file will be created.
