From: Tom Lord <lord@emf.net>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: ttn's build system [was: Extended -e syntax]
Date: Wed, 10 Mar 2004 15:22:00 -0800 (PST) [thread overview]
Message-ID: <200403102322.PAA10805@morrowfield.regexps.com> (raw)
In-Reply-To: <87n06uvuy4.fsf@ivanova.rotty.yi.org> (message from Andreas Rottmann on Sat, 06 Mar 2004 16:47:31 +0100)
> From: Andreas Rottmann <a.rottmann@gmx.at>
> [ Tom: Thien-Thi Nguyen has written a buildsystem for his Guile branch
> which uses autoconf, but replaces automake, suing Guile. I intend to
> make that play well with Arch, akin to your package-framework, so
> you might be interested in this message ]
Sort of. I cut my professional teeth working on build systems and
have some definate ideas about them. auto* (including -conf) is
... um ... suboptimal.
It would merit its own big-ass project to replace them in a
comprehensive way --- something I'm interested in but don't have much
bandwidth to work on. And, anyway, few people have enough experience
in this area to do it well or understand why a good design is good --
so volunteer contributions would be hard to shepherd. And also:
obtaining _adoption_ of new systems is steep uphill climb -- there's a
lot of inertia to overcome.
Personally, with due respect to the list, it's something I'm more
likely to want to work on once Pika is humming along rather than
before. It's an area that has pretty touchy requirements for the
scripting language used.
So, yes, I'm interested -- but no, I'm not about to delve into it in
depth.
-t
p.s.: why are package systems and configuration systems different
things? Makes no sense (other than historical) at all.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-03-10 23:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 3:32 Extended -e syntax Clinton Ebadi
2004-03-01 5:04 ` Andreas Rottmann
2004-03-01 11:10 ` Thien-Thi Nguyen
2004-03-01 14:27 ` Arch and Guile Andreas Rottmann
2004-03-01 19:04 ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14 ` ITLA Andreas Rottmann
2004-03-01 21:55 ` ITLA Tom Lord
2004-03-02 0:11 ` ITLA Andreas Rottmann
2004-03-02 2:50 ` ITLA Tom Lord
2004-03-02 14:04 ` ITLA Andreas Rottmann
2004-03-02 3:26 ` ITLA Miles Bader
2004-03-03 11:22 ` ITLA Neil Jerram
2004-03-03 11:55 ` ITLA Andreas Rottmann
2004-03-04 13:55 ` Archive of library modules for Guile Andreas Rottmann
2004-03-04 20:49 ` Neil Jerram
2004-03-04 23:00 ` Andreas Rottmann
2004-03-07 17:33 ` Thamer Al-Harbash
2004-03-07 18:17 ` Thien-Thi Nguyen
2004-03-01 23:07 ` Arch and Guile Thien-Thi Nguyen
2004-03-02 0:23 ` Andreas Rottmann
2004-03-03 13:01 ` Thien-Thi Nguyen
2004-03-01 11:21 ` Extended -e syntax Thien-Thi Nguyen
2004-03-01 20:20 ` Christopher Cramer
2004-03-02 4:55 ` Clinton Ebadi
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
2004-03-10 18:59 ` ttn's build system Andreas Rottmann
2004-03-10 22:28 ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22 ` Tom Lord [this message]
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=200403102322.PAA10805@morrowfield.regexps.com \
--to=lord@emf.net \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).