Canonical binary names

1 view
Skip to first unread message

William Stein

unread,
Feb 7, 2010, 9:33:32 PM2/7/10
to sage-devel, sage-release
Hi,

After procrastinating 3 years, I finally wrote a script to create
bdist's with fairly canonical names on different platforms. It's

http://boxen.math.washington.edu/home/wstein/bin/botdist

You just make sure it is in your PATH, and from SAGE_ROOT type

botdist

Note that the last line of that script will obviously only work for me
(so you would have to change it, or ignore the error, which is safe).

I'm currently using this to generate binaries for 4.3.2, which are
appearing here:

http://boxen.math.washington.edu/home/wstein/binaries/4.3.2/

I also put Alex Ghitza's contributed binary in the "other"
subdirectory, but I don't think the name is so good, so maybe it has
to be renamed.

William

--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

Georg S. Weber

unread,
Feb 8, 2010, 1:45:38 PM2/8/10
to sage-devel


Hooray!

Please add the following change/distinction: instead of "...-
PowerMacintosh-..." (a name the second part of which is superfluous
anyway, because of the "Darwin" at the end of the canonical naming
scheme), I propose to use:

...-PowerPC_G4-...

...-PowerPC_G5-...

according to the respective hardware the binary is produced on.
There's no automatic detection to distinguish a G4 from G5 yet, but
I'll think about it and let you know as soon as possible. In the
meantime, I'll (re-)name the OS X 10.4 PowerPC_G4 Sage-4.3.2 .dmg I've
just created accordingly.

Thanks a lot!


Cheers,
Georg

kcrisman

unread,
Feb 8, 2010, 2:19:38 PM2/8/10
to sage-devel
> > After procrastinating 3 years, I finally wrote a script to create
> > bdist's with fairly canonical names on different platforms.  It's
>
> >  http://boxen.math.washington.edu/home/wstein/bin/botdist
>

Nice!

> Hooray!
>
> Please add the following change/distinction: instead of "...-
> PowerMacintosh-..." (a name the second part of which is superfluous
> anyway, because of the "Darwin" at the end of the canonical naming
> scheme), I propose to use:
>
> ...-PowerPC_G4-...
>
> ...-PowerPC_G5-...
>
> according to the respective hardware the binary is produced on.
> There's no automatic detection to distinguish a G4 from G5 yet, but
> I'll think about it and let you know as soon as possible. In the
> meantime, I'll (re-)name the OS X 10.4 PowerPC_G4 Sage-4.3.2 .dmg I've
> just created accordingly.

Unfortunately, the script above doesn't (or does it?) yet distinguish
between PPC and Intel, so does not solve http://trac.sagemath.org/sage_trac/ticket/7623
. Georg, would that be fairly easy to do, though? This script could
be then named sage-auto-bdist or something like that and put in /local/
bin.

- kcrisman

William Stein

unread,
Feb 8, 2010, 3:09:11 PM2/8/10
to sage-...@googlegroups.com
On Mon, Feb 8, 2010 at 11:19 AM, kcrisman <kcri...@gmail.com> wrote:
>> > After procrastinating 3 years, I finally wrote a script to create
>> > bdist's with fairly canonical names on different platforms.  It's
>>
>> >  http://boxen.math.washington.edu/home/wstein/bin/botdist
>>
>
> Nice!
>
>> Hooray!
>>
>> Please add the following change/distinction: instead of "...-
>> PowerMacintosh-..." (a name the second part of which is superfluous
>> anyway, because of the "Darwin" at the end of the canonical naming
>> scheme), I propose to use:
>>
>> ...-PowerPC_G4-...
>>
>> ...-PowerPC_G5-...
>>
>> according to the respective hardware the binary is produced on.
>> There's no automatic detection to distinguish a G4 from G5 yet, but
>> I'll think about it and let you know as soon as possible. In the
>> meantime, I'll (re-)name the OS X 10.4 PowerPC_G4 Sage-4.3.2 .dmg I've
>> just created accordingly.
>
> Unfortunately, the script above doesn't (or does it?) yet distinguish
> between PPC and Intel,

Example OS X names are:

sage-4.3.2-OSX-32bit-10.5-i386-Darwin.dmg
sage-4.3.2-OSX-32bit-10.5-PowerMacintosh-Darwin.dmg
sage-4.3.2-OSX-64bit-10.6-i386-Darwin.dmg

The script I wrote *ONLY* has anything to do with this part of the
name: "sage-4.3.2-OSX-32bit-10.5".
The Sage "sage-bdist" script postpends "-i386-Darwin.dmg" to the name.
Thus your request about
PowerPC versus PowerMacintosh isn't relevant directly to my script,
but to the sage-bdist command.

> so does not solve http://trac.sagemath.org/sage_trac/ticket/7623
> .  Georg, would that be fairly easy to do, though?  This script could
> be then named sage-auto-bdist or something like that and put in /local/
> bin.
>
> - kcrisman
>

> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org

Georg S. Weber

unread,
Feb 8, 2010, 4:51:45 PM2/8/10
to sage-devel
> Example OS X names are:
>
> sage-4.3.2-OSX-32bit-10.5-i386-Darwin.dmg
> sage-4.3.2-OSX-32bit-10.5-PowerMacintosh-Darwin.dmg
> sage-4.3.2-OSX-64bit-10.6-i386-Darwin.dmg
>
> The script I wrote *ONLY* has anything to do with this part of the
> name: "sage-4.3.2-OSX-32bit-10.5".
> The Sage "sage-bdist" script postpends "-i386-Darwin.dmg" to the name.
>  Thus your request about
> PowerPC versus PowerMacintosh isn't relevant directly to my script,
> but to the sage-bdist command.
>

You're right of course,
I should have looked more closely at the .dmgs I produce regularly ...
:-)


Cheers,
Georg

Reply all
Reply to author
Forward
0 new messages