From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: Daniel Skarda <0rfelyus@ucw.cz>, guile-devel@gnu.org
Subject: Adding stuff to the core distro (was Re: Infix syntax)
Date: Wed, 9 Oct 2002 00:40:02 +0200 [thread overview]
Message-ID: <15779.24258.322274.433450@blauw.xs4all.nl> (raw)
In-Reply-To: <m37kgsbnvf.fsf@laruns.ossau.uklinux.net>
neil@ossau.uklinux.net writes:
> principles on this point.
>
> I'm not sure what to suggest, myself. Seems to me that one extreme is
> the Emacs approach - basically bundle everything. The convenience of
> the opposite extreme depends on what kind of package repository system
> (aka GUMM) we can create.
>
> Any clarifying ideas, anyone?
Yes: bundle anything that is usable/finished and documented. All
package documentation should be in the reference manual, or perhaps in
a separate package-manual.
The beauty of using python is that I can go to the python doc-dir,
and do
grep 'whatever-I-need' *.tex,
(or sometimes even,
rpm -ql python| grep 'whatever-I-need' )
and I know directly if it's supported. No hassle with looking around
for relevant webpages, or finding out how to install it.
Perhaps it makes for easier logistics if all packes were in a separate
tarball, due to release frequencies -- don't know about that.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-08 22:40 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 [this message]
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
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=15779.24258.322274.433450@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--cc=0rfelyus@ucw.cz \
--cc=guile-devel@gnu.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).