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

On Tue, Dec 15, 2015 at 6:09 AM, Sean Whitton wrote: > 1) Use the nocheck build profile to build and upload f-el without >running its tests. Then build and upload shut-up and undercover. >Then build and upload a full version of f-el. > > 2) Use the nocheck build profile to build and

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

* Paul Wise , 2015-12-15, 18:43: On Tue, Dec 15, 2015 at 6:09 AM, Sean Whitton wrote: 1) Use the nocheck build profile to build and upload f-el without running its tests. Then build and upload shut-up and undercover. Then build and upload a full version of f-el. 2) Use the

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

Sean Whitton 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

Re: Cask & dependencies

Sean Whitton writes: > > After: > , > | EMACSFLAGS = -L /usr/share/emacs/site-lisp/dash-el \ > | -L /usr/share/emacs/site-lisp/elpa-src/noflet-* > | test : > | $(EMACS) --no-site-file --no-site-lisp --batch \ > | $(EMACSFLAGS) \ > |

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

On Mon, Dec 14, 2015 at 09:04:00PM -0400, David Bremner wrote: > 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. I've dug a

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

Hello, As I mentioned there's a dependency loop in building f-el [1]. This is a library that a lot of Emacs addons depend on. If we could get this into the archive we would have dash-el, s-el and f-el all in Debian and future dependency resolution would be much easier. The problem is that

Cask & dependencies

Hello, I'm working on packaging the dependencies and build dependencies of projectile [1], and I'm trying to ensure that the test suites of all dependencies and build dependencies are run when the packages are built. Unfortunately there is a dependency circle within the dependencies and build