From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org, Joshua Judson Rosen <rozzin@geekspace.com>
Subject: Re: apt based package dist for guile?
Date: Tue, 05 Aug 2003 16:41:53 -0400 [thread overview]
Message-ID: <m365lb96qg.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <20030805201840.GA10216@www>
rm@fabula.de wrote:
> The one tempting thing about CPAN (and apt, here's where they meet)
> is the simple, unified build/install process -- either 'apt-get install foo'
> or CPAN's 'download / perl Makefile.PL / make / make install' process.
Perl's MakeMaker means that the build system for a Perl module is the
same as that of other Perl modules, but it's gratuitously different
from that of all other packages. There's no reason that a package's
build system should be based on the fact that it happens to be an
extension of a particular scripting language. It's better to stick
with an existing build system that people already know (e.g.,
autoconf, or whatever you would normally use for anything else). It
makes sense to put together some rules (m4 macros for autoconf, or
whatever) that can be reused for all modules for a particular
scripting language, but there's no reason to stick the installing user
with a different interface.
paul
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-08-05 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 11:32 apt based package dist for guile? Nic
2003-08-03 23:41 ` MJ Ray
2003-08-04 8:44 ` Nic
2003-08-04 16:31 ` Thamer Al-Harbash
2003-08-05 13:45 ` Joshua Judson Rosen
2003-08-05 17:29 ` Thamer Al-Harbash
2003-08-05 20:18 ` rm
2003-08-05 20:41 ` Paul Jarc [this message]
2003-08-05 20:48 ` Nic
2003-08-05 21:15 ` Paul Jarc
2003-08-05 22:16 ` Thamer Al-Harbash
2003-08-05 23:02 ` Paul Jarc
2003-08-05 22:16 ` MJ Ray
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=m365lb96qg.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=guile-user@gnu.org \
--cc=rozzin@geekspace.com \
/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).