Bug#1057313: racket: Please build and install Zuo

[David Bremner]

G. Weinholt  writes:


> I mean, I could easily package Zuo separately. I could do the first
> upload and put the Scheme team as maintainer so anyone who needs to can
> update it. I'm guessing you would still use the copy that comes as part
> of Racket to build Racket, though.
>

Sure, don't let me stand in the way. Maybe when things stabilize we can
eliminate the duplication / embedding.

d

Bug#1057313: racket: Please build and install Zuo

[G . Weinholt]

David Bremner  writes:

> "G. Weinholt"  writes:
>
>> Does it seem reasonable to build and install a zuo package from the
>> Racket source package? Alternatively, I could package zuo separately
>> using the above repository. They haven't tagged any releases though.
>
> I don't really object to adding another binary package if it's just a
> matter of listing what files to install.

That's what I would hope would be needed, but maybe it's impractical.

> I can't promise to do snapshot
> releases between racket releases though, so it depends a bit on the pace
> of development (and whether there are any complications like building
> with different options).

Precisely. I hope that Chez Scheme will not normally need any bleeding
edge features from Zuo. However, I tried building chezscheme with Zuo
from racket 8.10+dfsg1-2 and it doesn't work:

| bin/zuo ta6le MAKE="make"
| checking boot files for ta6le against pb
| make-targets: bad specification line: (list ':target 'build (list 
"pb/bin/pb/scheme" "pb/bin/pb/petite" 'revision) # ':recur)
|  in for-each
|  in make-targets
|  in build-one
|  in loop
|  in module->hash
| make: *** [Makefile:10: build] Error 1

There is a changelog entry for Zuo 1.8 that mentions support for :recur
and zuo.c in racket 8.10+dfsg1 says it is version 1.6.

So this is already not working. :) Version 8.11.1 comes with Zuo 1.7. So
the next chezscheme release would need a version of racket that hasn't
been released yet.

I mean, I could easily package Zuo separately. I could do the first
upload and put the Scheme team as maintainer so anyone who needs to can
update it. I'm guessing you would still use the copy that comes as part
of Racket to build Racket, though.

What do you think?

-- 
Sitting in muddy water
isn't such as a bad life
if it ends after the first time

Bug#1057313: racket: Please build and install Zuo

[David Bremner]

"G. Weinholt"  writes:

> Package: racket
> Version: 8.10+dfsg1-2
> Severity: wishlist
> X-Debbugs-Cc: debian-sch...@lists.debian.org
>
> Hello David,
>
> I'm looking at the upcoming Chez Scheme release and I see that it has
> a build-dependency on Zuo :
>
>   "This is a mirror of the Zuo sources in the racket/src/zuo directory of
>   the Racket repository."
>
> Does it seem reasonable to build and install a zuo package from the
> Racket source package? Alternatively, I could package zuo separately
> using the above repository. They haven't tagged any releases though.

I don't really object to adding another binary package if it's just a
matter of listing what files to install. I can't promise to do snapshot
releases between racket releases though, so it depends a bit on the pace
of development (and whether there are any complications like building
with different options).

d

Bug#1057313: racket: Please build and install Zuo

[G. Weinholt]

Package: racket
Version: 8.10+dfsg1-2
Severity: wishlist
X-Debbugs-Cc: debian-sch...@lists.debian.org

Hello David,

I'm looking at the upcoming Chez Scheme release and I see that it has
a build-dependency on Zuo :

  "This is a mirror of the Zuo sources in the racket/src/zuo directory of
  the Racket repository."

Does it seem reasonable to build and install a zuo package from the
Racket source package? Alternatively, I could package zuo separately
using the above repository. They haven't tagged any releases though.

/weinholt

-- 
Sitting in muddy water
isn't such as a bad life
if it ends after the first time