From: rm@fabula.de
Cc: guile-user@gnu.org, Joshua Judson Rosen <rozzin@geekspace.com>
Subject: Re: apt based package dist for guile?
Date: Tue, 5 Aug 2003 22:18:40 +0200 [thread overview]
Message-ID: <20030805201840.GA10216@www> (raw)
In-Reply-To: <Pine.BSF.4.51.0308051313210.46324@helena.whitefang.com>
On Tue, Aug 05, 2003 at 01:29:28PM -0400, Thamer Al-Harbash wrote:
> On Tue, 5 Aug 2003, Joshua Judson Rosen wrote:
>
> > On Mon, Aug 04, 2003 at 12:31:53PM -0400, Thamer Al-Harbash wrote:
> >
> > > I'd sooner stick a needle in my eye than use a CPAN like system.
> >
> > Why is that?
>
> Sorry for the knee jerk reaction. This isn't the forum to knock
> other packaging systems.
>
> There are too many reasons to list. I could probably discuss the
> pros and cons for hours. Suffice it to say that for operating
> systems which you want to ship to users and keep up to date
> yourself, using a packaging system with automatic dependency
> tracking is great.
Are you refering to Debian's apt system (authomatic 'up-to-date')
or to CPAN (Perl's package archive)?
The two systems are arather different, esp. when it comes to
the "issues" you mention.
> For a programming environment this is not the case. Making this
> inpersonal, automatic, and "always up to date" is not necessarily
> good. You go from shipping a really nice Scheme
> interpreter/library to shipping a virtual plastform.
>
> My own feeling is that there should be a maintainer or two that
> keeps track of stable guile software and keep a directory up to
> date.
The idea of 'stable' is rather what apt tries. You do _not_ get
software that is "up to date" but rather a stable snapshot, that
sometimes can be (and often is) rather outdated (but stable).
CPAN is just the other half of your suggestion: a list/directory of
stable packages/modules (and by no means a platform).
> This process can also be automated by having programmers
> submit their projects for listing. We already have freshmeat, and
> the Free Software Directory. These two directories can serve this
> purpose well enough as it is.
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.
[or, from the developer's side: a build system that helps to create
a .dpkg or even a module that wraps the build/install process like
MakeMaker.pm]
Ralf Mattes
> --
> Thamer Al-Harbash
> GPG Key fingerprint: D7F3 1E3B F329 8DD5 FAE3 03B1 A663 E359 D686 AA1F
> "to understand recursion first one must understand recursion"
>
>
> _______________________________________________
> Guile-user mailing list
> Guile-user@gnu.org
> http://mail.gnu.org/mailman/listinfo/guile-user
_______________________________________________
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:18 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 [this message]
2003-08-05 20:41 ` Paul Jarc
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=20030805201840.GA10216@www \
--to=rm@fabula.de \
--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).