From: Lynn Winebarger <owinebar@free-expression.org>
Cc: Neil Jerram <neil@ossau.uklinux.net>, guile-devel@gnu.org
Subject: Re: Adding stuff to the core distro (was Re: Infix syntax)
Date: Thu, 10 Oct 2002 17:24:04 -0500 [thread overview]
Message-ID: <02101017240400.07034@locke.free-expression.org> (raw)
In-Reply-To: <87u1jub4lh.fsf@raven.i.defaultvalue.org>
On Thursday 10 October 2002 12:12, Rob Browning wrote:
> Daniel Skarda <0rfelyus@ucw.cz> writes:
>
> > I my opinion, breaking guile into small (orthogonal) packages is
> > nice from "pure" developer's view, but it fails in "real world" and
> > builds unnecessary walls between Guile and Joe Average Programmer,
> > who wants to evaluate Guile:
>
> I wouldn't propose that we break guile up into a "maze of twisty
> packages", but I do think that long-term, maintaining some divisions
> may make sense. I'm not even sure we necessarily need to do anything
> wrt to guile-core as it stands -- for the most part, I'm interested in
> what we might do going forward.
>
> IMO whether or not we break up the *source-tree* is a different
> question from what we do at install time, and what policies we adopt
> wrt interdependencies inside and outside guile-core. For example, we
> might decide to have a very large source tree that by default installs
> everything, but can also just install parts of itself. Maybe
X is the real example of this "throw everything into one big honkin' pot
and pray" approach. What a beast it is, too. Regardless of how guile
is packaged to the end user (and that's not really J. guile hacker's
job in many respects), more code barriers are better. Keeping the
trees separate is a proactive measure for preventing code incest.
So to speak.
Lynn
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-10 22:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 11:26 Infix syntax Daniel Skarda
2002-10-05 8:55 ` Neil Jerram
2002-10-06 8:05 ` Daniel Skarda
2002-10-08 21:51 ` Adding stuff to the core distro (was Re: Infix syntax) Neil Jerram
2002-10-08 22:40 ` Han-Wen Nienhuys
2002-10-09 3:30 ` Rob Browning
2002-10-09 18:15 ` Neil Jerram
2002-10-09 20:17 ` Rob Browning
2002-10-10 12:20 ` Daniel Skarda
2002-10-10 12:29 ` Daniel Skarda
2002-10-13 14:28 ` Neil Jerram
2002-10-16 21:35 ` Daniel Skarda
2002-10-19 4:50 ` tomas
2002-10-20 19:15 ` Daniel Skarda
2002-10-21 9:36 ` tomas
2002-10-21 18:21 ` Neil Jerram
2002-10-19 22:17 ` Christopher Cramer
2002-10-20 19:05 ` Daniel Skarda
2002-10-10 16:06 ` Daniel Skarda
2002-10-10 17:12 ` Rob Browning
2002-10-10 18:46 ` Clinton Ebadi
2002-10-10 22:24 ` Lynn Winebarger [this message]
2002-10-13 15:09 ` Proposal for scope of core distro Neil Jerram
2002-10-17 0:10 ` Adding stuff to the core distro (was Re: Infix syntax) Daniel Skarda
2002-10-18 7:24 ` Lynn Winebarger
2002-10-20 20:25 ` Daniel Skarda
2002-10-10 18:08 ` Bill Gribble
2002-10-17 2:42 ` Daniel Skarda
2002-10-13 14:27 ` Neil Jerram
2002-10-17 1:25 ` Daniel Skarda
2002-10-19 10:56 ` Neil Jerram
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=02101017240400.07034@locke.free-expression.org \
--to=owinebar@free-expression.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).