[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

On Sun, Aug 1, 2010 at 23:17, Far? <fahree at gmail.com> wrote:
> 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?

The cl-asdf dependency of c-l-c is hardcoded in debian/control, the
c-l-c dependency of cl-asdf is generated by dh_lisp when building.

Installing c-l-c does not depend on cl-asdf, but its code depends.

> 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.

I'll do it.

> 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.

The two packages confuse me.  Can anyone analyze their dependencies

> 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?

I've uploaded the previous version of c-l-c, but I think all the
members besides you are all in charge of it.

The orig tarball is only required if the package is not debian native.
Do not put debian revision part in your version number [1], simply
increase the version number.  You can use `dch -i'.

[1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version

Reply to: