[Sbcl-devel] 0.7.13 binaries

I'm producing 0.7.13 binary packages for Linux/PPC and Linux/Alpha,
which will appear when ready at
http://ftp.linux.org.uk/pub/lisp/sbcl/
(the PPC one is already there; the Alpha binary I have to recompile
first, because it got wiped out by a cron job this morning). If they
can be added to the Sourceforge file release thing, that would be
cool.
Also in the same place is a copy of CLX for SBCL 0.7.13, packaged to
use the 0.7.13 contribized asdf and socket library. That may be less
appropriate for copying to sourceforge, because it exists on its own
development timetable rather than being tied to SBCL releases, but
if you want to put a pointer on the web pages, it won't be going away
any time soon
-dan
--
http://www.cliki.net/ - Link farm for free CL-on-Unix resources

Thread view

I'm producing 0.7.13 binary packages for Linux/PPC and Linux/Alpha,
which will appear when ready at
http://ftp.linux.org.uk/pub/lisp/sbcl/
(the PPC one is already there; the Alpha binary I have to recompile
first, because it got wiped out by a cron job this morning). If they
can be added to the Sourceforge file release thing, that would be
cool.
Also in the same place is a copy of CLX for SBCL 0.7.13, packaged to
use the 0.7.13 contribized asdf and socket library. That may be less
appropriate for copying to sourceforge, because it exists on its own
development timetable rather than being tied to SBCL releases, but
if you want to put a pointer on the web pages, it won't be going away
any time soon
-dan
--
http://www.cliki.net/ - Link farm for free CL-on-Unix resources

I've just put up x86 rpms. I'm pretty excited about the new
asdf/contrib stuff. I think it will make it a lot easier to distribute
packages.
One potential issue created by the rpm builds: rpm likes to configure
packages with one prefix and then install them into a separate scratch
prefix. Usually like this:
./configure --prefix=/usr
make install prefix=/var/tmp/$package-root/usr
The potential problem here is that if packages add rpaths to the
libraries they create they have to respect the prefix passed in
configure and not in install. Right now the install.sh script doesn't
distinguish the two. I'm not sure if this is a real issue. Will we
ever need rpaths in sbcl contrib libraries?
One other question. Should the sbcl contribs be in a separate rpm
package or should they be included in the main package?
miles

Miles Egan <miles@...> writes:
> One other question. Should the sbcl contribs be in a separate rpm
> package or should they be included in the main package?
My opinion is that they should be treated as part of SBCL. We already
run tests on the contribs, and only those that still "work" come as
part of the binary or are installed. Also, their use and further
development is something that I think I want to encourage... since we
already require (ho ho) active requests to include a contrib into the
Lisp image, it's probably not worth having a second barrier to getting
the goodies :-)
Cheers,
Christophe
--
http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)

On Thu, Feb 27, 2003 at 12:12:10AM +0000, Daniel Barlow wrote:
> I'm producing 0.7.13 binary packages for Linux/PPC and Linux/Alpha,
> which will appear when ready at
>
> http://ftp.linux.org.uk/pub/lisp/sbcl/
>
> (the PPC one is already there; the Alpha binary I have to recompile
> first, because it got wiped out by a cron job this morning). If they
> can be added to the Sourceforge file release thing, that would be
> cool.
I've added the files to the distribution, thank you. And if you could
come up with a signed sbcl-0.7.13-dan_b.asc file, I can add that too.
Alternatively, I don't mind adding files myself, but if you ever want
to avoid delay, I think SourceForge lets you -- any official developer
on the project -- put files into distributions directly. From the main
page, follow the "Admin" link, then "Edit/Release Files", then "Edit
Releases", etc.
(The lengthy delay this time was not just because I'm a lazy fellow
but because balefire delenda est -- complete hard drive titsupitude,
probably not worth repairing in an older laptop. So I've been
distracted by progressively rebuilding by adapting backed-up OpenBSD
configuration stuff to my fast relatively new Linux box, and I've had
more fun than I really wanted with Internet connectivity stuff in
general and exim in particular.)
> Also in the same place is a copy of CLX for SBCL 0.7.13, packaged to
> use the 0.7.13 contribized asdf and socket library. That may be less
> appropriate for copying to sourceforge, because it exists on its own
> development timetable rather than being tied to SBCL releases, but
> if you want to put a pointer on the web pages, it won't be going away
> any time soon
OK, I've added the link in the libs.php page.
While I was there, I also deleted the old link from libs.php to
db-sockets as a standalone library, on the theory that it's probably
superseded by the contrib/ version now. And I kept the link from
libs.php to <http://ww.telent.net/lisp/&gt;, but I note that that page
says things like "* New 2000-05-30" so let me know if you'd like that
link to go somewhere else.
--
William Harold Newman <william.newman@...>
"Build a man a fire, and he'll be warm for a day. Set a man on fire,
and he'll be warm for the rest of his life." -- Terry Pratchett
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C