Bug#591054: cl-asdf: circular dependency with common-lisp-controller

[Faré]

I tried to upload a cl-asdf that removes the dependency, but failed.

1- with the new ASDF2, do we really need to register source anymore, anyway?
 It should already be registered, being in the correct location that's
registered by default.

2- should c-l-c depend on ASDF if ASDF depends on c-l-c? How do the
configuration
 script currently resolve the dependency issue?

I believe that
a- c-l-c should be simplified with respect to the newest ASDF2, and
marked as depending on ASDF 2.004 or later.
b- dh_lisp should be simplified with respect to said new c-l-c
c- cl-asdf would then not depend on c-l-c anymore.

Who on the debian CL team is in charge of c-l-c? If no one, would
anyone upload my changes? How do I upload a -2 package on mentors with
it complaining that there is no orig tarball?

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Amateurs talk strategy. Professionals talk logistics. - old military saying

On 31 July 2010 10:03, Bill Allombert <ballombe at debian.org> wrote:
> Package: cl-asdf
> Version: 2:2.004-1
> Severity: important
>
> Hello Debian Common Lisp Team,
>
> There is a circular dependency between cl-asdf and common-lisp-controller:
>
> cl-asdf                 :Depends: common-lisp-controller (>= 5.11)
> common-lisp-controller  :Depends: cl-asdf (>= 1.625)
>
> Circular dependencies are known to cause problems during upgrade, so we
> should try to get rid of them.
>
> See threads
> http://lists.debian.org/debian-devel/2005/06/msg02111.html
> http://lists.debian.org/debian-devel/2005/11/msg01101.html
>
> Cheers,
> --
> Bill. <ballombe at debian.org>
>
> Imagine a large red swirl here.
>