From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-lisp+bounces-140-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1OPbeZ-0001LZ-ST
	for garchives@archives.gentoo.org; Fri, 18 Jun 2010 13:30:40 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 2C717E08F4;
	Fri, 18 Jun 2010 13:30:33 +0000 (UTC)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25])
	by pigeon.gentoo.org (Postfix) with ESMTP id 095F5E08F4
	for <gentoo-lisp@lists.gentoo.org>; Fri, 18 Jun 2010 13:30:32 +0000 (UTC)
Received: from compute2.internal (compute2.internal [10.202.2.42])
	by gateway1.messagingengine.com (Postfix) with ESMTP id 8D4C8FBF00;
	Fri, 18 Jun 2010 09:30:13 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
  by compute2.internal (MEProxy); Fri, 18 Jun 2010 09:30:13 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version; s=smtpout; bh=2r/OVjMwH/SK6qOW91mFeLRhQMQ=; b=STBtYQAfioJdFMjp5+U8QeqPznQ81cAG0Rs+x06igxh9cmuu6MlmfJ3h2BOIfcbEu0auYACE87scfSMS4xnbkYmw95geDi2f4St9U7mb4xQMZqR4SaAsiwcYWH52LyIE0iEXWeaNo1exk88HL0eVyQWBvOmxUzsEGVc+AUfQpSg=
X-Sasl-enc: umY1uH0q4/kk6Y9TonzyFc8jw8klDBXSWJcHU4+48+X7 1276867810
Received: from [10.10.10.10] (unknown [115.134.227.5])
	by mail.messagingengine.com (Postfix) with ESMTPSA id A28D34DFCC1
	for <gentoo-lisp@lists.gentoo.org>; Fri, 18 Jun 2010 09:30:10 -0400 (EDT)
Subject: Re: [gentoo-lisp] [RFC] A couple of ideas
From: Stelian Ionescu <sionescu@cddr.org>
To: gentoo-lisp@lists.gentoo.org
In-Reply-To: <4C1AE7CE.6010003@gentoo.org>
References: <4C1AE7CE.6010003@gentoo.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-oLNIQSfnlDO8+A5oWuUV"
Date: Fri, 18 Jun 2010 21:30:05 +0800
Message-ID: <1276867806.24313.67.camel@blackhole.cddr.org>
Precedence: bulk
List-Post: <mailto:gentoo-lisp@lists.gentoo.org>
List-Help: <mailto:gentoo-lisp+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-lisp+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-lisp+subscribe@lists.gentoo.org>
List-Id: Gentoo Lisp mail <gentoo-lisp.gentoo.org>
X-BeenThere: gentoo-lisp@lists.gentoo.org
Mime-Version: 1.0
X-Mailer: Evolution 2.30.1.2 
X-Archives-Salt: 2d48c53a-e8f7-4caf-bf4d-16501d714bc0
X-Archives-Hash: 9419ec91e51104beb0f7daaeddafcaa6


--=-oLNIQSfnlDO8+A5oWuUV
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2010-06-18 at 00:28 -0300, Tom=C3=A1s Touceda wrote:
> Hello everyone,
>=20
> So a couple of days ago we discussed with pchrist about how we will
> handle porting almost everything in the lisp-overlay to the main tree.
> We need feedback on the following ideas to solve this, so please critic
> and comment on this.
>=20
> The first idea is to move all the cl-* packages from the main tree to a
> new overlay different from the official one, so we can have a clean
> start in the main tree. Since most of these packages are broken (meaning
> bad src_uri, bad deps, and who knows what else at this point), we
> thought that this won't hurt the users. Most of us are using what's in
> the overlay (and whoever isn't, please do), but either way the packages
> aren't going to disappear they're just being moved, so don't panic :).

That's a good idea

> The second idea is for mirroring all the tarballs that the cl-* packages
> use. Why do this? Well, most cl packages don't have a versioned tarball,
> so this brings a couple of problems regarding digests, and basic version
> control, so what we want to do is to build a little system to facilitate
> this job.
>=20
> Here's what I've written about this second idea:
>=20
> ****** Start ******
>=20
> The problem:
>=20
> Lisp packages' upstream don't name their tarballs with version numbers.
> When there's a new release, the tarball digest changes, and then the
> package digest fails.

That's not always true: some do this, but not all. The problem is more
with those that do not do releases at all, and just want you to get
stuff from the live repository

> A posible solution:
>=20
> Build an app that controls when the tarballs are updated and notifies
> us about it in some way, and that provides a way of mirroring the tarball=
.
>=20
> Application design:
[snip]

To me, using python and XML seems quite excessive. bash + wget + md5sum
and some simple text files is a lot easier to deal with
Also, there are a few other projects that try to write a package manager
for lisp(lispy, clbuild, quicklisp, clornucopia, a couple others that I
can't remember right now). We could join forces and have a single point
of collection for versioned tarballs and snapshots

--=20
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
http://common-lisp.net/project/iolib

--=-oLNIQSfnlDO8+A5oWuUV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEABECAAYFAkwbdN0ACgkQjWsER8+9ASX9DQCeMkhQs1381IidwRHeF+nHZ3z5
gPQAmQHTeUya971VtkHih6Vopok/Vbel
=5g3P
-----END PGP SIGNATURE-----

--=-oLNIQSfnlDO8+A5oWuUV--