Darren Bane writes:
> I don't use the OO paradigm that often, but ended up hacking YASOS
> from SLIB to live in a Scheme 48 module for those times that I do.
> I figured this would be more portable anyway (i.e. to every impl
> that supports SLIB).
That's a good idea. I thought about using SLIB anyway.
I'd like to port my package buid system from shell scripts to scsh and
I think that it makes sense to use the OO paradigm. The base case is
the packages that can be built with autoconf and make. Packages that
need different or additional build instructions are derived from the
On the other hand, I could simply overwrite default top-level
definitions with package specific definitions. For example, I could
complete the default definitions
(define name #f)
(define licenses '("GPL-2"))
(&& (sh configure ,configure-options)
(define name "scsh")
(define licenses '("BSD-style License"))
Hm, this approach is much simpler. I'll probably do it this way.