| 1 |
On Fri, 2010-06-18 at 00:28 -0300, Tomás Touceda wrote: |
| 2 |
> Hello everyone, |
| 3 |
> |
| 4 |
> So a couple of days ago we discussed with pchrist about how we will |
| 5 |
> handle porting almost everything in the lisp-overlay to the main tree. |
| 6 |
> We need feedback on the following ideas to solve this, so please critic |
| 7 |
> and comment on this. |
| 8 |
> |
| 9 |
> The first idea is to move all the cl-* packages from the main tree to a |
| 10 |
> new overlay different from the official one, so we can have a clean |
| 11 |
> start in the main tree. Since most of these packages are broken (meaning |
| 12 |
> bad src_uri, bad deps, and who knows what else at this point), we |
| 13 |
> thought that this won't hurt the users. Most of us are using what's in |
| 14 |
> the overlay (and whoever isn't, please do), but either way the packages |
| 15 |
> aren't going to disappear they're just being moved, so don't panic :). |
| 16 |
|
| 17 |
That's a good idea |
| 18 |
|
| 19 |
> The second idea is for mirroring all the tarballs that the cl-* packages |
| 20 |
> use. Why do this? Well, most cl packages don't have a versioned tarball, |
| 21 |
> so this brings a couple of problems regarding digests, and basic version |
| 22 |
> control, so what we want to do is to build a little system to facilitate |
| 23 |
> this job. |
| 24 |
> |
| 25 |
> Here's what I've written about this second idea: |
| 26 |
> |
| 27 |
> ****** Start ****** |
| 28 |
> |
| 29 |
> The problem: |
| 30 |
> |
| 31 |
> Lisp packages' upstream don't name their tarballs with version numbers. |
| 32 |
> When there's a new release, the tarball digest changes, and then the |
| 33 |
> package digest fails. |
| 34 |
|
| 35 |
That's not always true: some do this, but not all. The problem is more |
| 36 |
with those that do not do releases at all, and just want you to get |
| 37 |
stuff from the live repository |
| 38 |
|
| 39 |
> A posible solution: |
| 40 |
> |
| 41 |
> Build an app that controls when the tarballs are updated and notifies |
| 42 |
> us about it in some way, and that provides a way of mirroring the tarball. |
| 43 |
> |
| 44 |
> Application design: |
| 45 |
[snip] |
| 46 |
|
| 47 |
To me, using python and XML seems quite excessive. bash + wget + md5sum |
| 48 |
and some simple text files is a lot easier to deal with |
| 49 |
Also, there are a few other projects that try to write a package manager |
| 50 |
for lisp(lispy, clbuild, quicklisp, clornucopia, a couple others that I |
| 51 |
can't remember right now). We could join forces and have a single point |
| 52 |
of collection for versioned tarballs and snapshots |
| 53 |
|
| 54 |
-- |
| 55 |
Stelian Ionescu a.k.a. fe[nl]ix |
| 56 |
Quidquid latine dictum sit, altum videtur. |
| 57 |
http://common-lisp.net/project/iolib |
Archives