From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: mvo@zagadka.ping.de, guile-user@gnu.org
Subject: Re: What if Guile changed its license to be LGPL?
Date: Wed, 05 Jun 2002 19:52:41 -0700 [thread overview]
Message-ID: <E17FnOD-0001r5-00@giblet> (raw)
In-Reply-To: <m3adq9ohjo.fsf@laruns.ossau.uklinux.net> (message from Neil Jerram on 05 Jun 2002 16:45:47 +0100)
From: Neil Jerram <neil@ossau.uklinux.net>
Date: 05 Jun 2002 16:45:47 +0100
- a consistent approach to factoring non-core functionality out of
core libguile
- a consistent approach to linking in such optional functionality and
handling any runtime licence implications that result
- a consistent approach to coping with the non-existence of optical
functionality
all these are part of build methodology. see below for 1.4.x ROADMAP
(under $w/build/dist-files locally) -- critique welcome.
- consistent usage of `features' and/or `cond-expand' to permit
programs to discover what optional functionality is present.
how do these interact w/ each other? are there weird corner cases?
thi
_________________________________________________________
This file explains the general direction of Guile.
1.4.x Goals
- No breakage for current usage.
- Build methodology evolved into architecture/implementation.
- Build methodology documented and exported.
- Scheme compilation to native code supported by build methodology.
By the end of 1.4.x, we want to be able to use guile maximally
from a "scheme world" point of view, reaching out from that
centrality to the hardware and everything in between, and do so
w/o forgetting how we did things before.
The key task here is to understand what the hell we're doing.
Then we put a name on it, put in place general machinery to
handle that case and any historic cases, and lastly re-work
these methodologies into scripts w/ parameters specific to Guile
and documentation explaining how to specialize the scripts.
Scripts then go under "guile-tools".
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-06-06 2:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 19:36 What if Guile changed its license to be LGPL? Marius Vollmer
2002-06-04 20:11 ` Per Bothner
2002-06-04 21:28 ` Marius Vollmer
2002-06-04 21:55 ` Per Bothner
2002-06-05 7:05 ` tomas
2002-06-05 22:54 ` Marius Vollmer
2002-06-05 23:08 ` Per Bothner
2002-06-05 23:31 ` Marius Vollmer
2002-06-06 12:33 ` Panagiotis Vossos
2002-06-05 23:07 ` Marius Vollmer
2002-06-04 21:59 ` Marius Vollmer
2002-06-05 15:45 ` Neil Jerram
2002-06-05 22:45 ` Marius Vollmer
2002-06-06 2:36 ` Thien-Thi Nguyen
2002-06-06 2:52 ` Thien-Thi Nguyen [this message]
2002-06-05 21:57 ` Dale P. Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E17FnOD-0001r5-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.org \
--cc=mvo@zagadka.ping.de \
--cc=ttn@glug.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).