Re: f.el dependency loop (was: Re: Cask & dependencies)

[David Bremner <david@tethera.net>]

Sean Whitton <spwhitton@spwhitton.name> writes:

>
> 3) Disable running f-el's test suite at package build time, but supply a
>    autopkgtest so the tests will still get run in ci.debian.org.
>
> 4) Disable running undercover.el's test suite at package build time, but supply a
>    autopkgtest so the tests will still get run in ci.debian.org.
>
> What would be best?  Options (3) and (4) avoid introducing a new
> bootstrapping loop into the Debian archive.  But on the other hand maybe
> such a bootstrapping loop is okay because all these packages are
> architecture independent.

My initial opinion is to avoid a bootstrapping loop. That might be
partially because I've never really used build profiles before, but also
it seems to more or less double the number of sponsored uploads you'd
need.

d