Eliminate the call to digestgen in EbuildBuild._fetchonly_exit,
and make Scheduler._generate_digests call it earlier when
--fetchonly is enabled. This avoids event loop recursion which
is not compatible with asyncio (digestgen makes many calls that
can trigger event loop recursion).
X-Gentoo-bug:
Replace a synchronous spawn_nofetch call with an asynchronous one,
in order to avoid event loop recursion which is not compatible with
asyncio. This involves refactoring of spawn_nofetch to provide an
asynchronous interface.
X-Gentoo-bug: 614116
X-Gentoo-bug-url:
-backup/zbackup 20170224-07:32 gokturk 29f1455481e
app-crypt/cfssl20170331-00:23 mrueg252aad347a9
app-crypt/yubikey-manager 20170402-05:44 gokturk 06c817d3f3a
app-text/jo20170330-12:46 jer 251ad0a696f
dev-ada/gnat_util
Add an async_unlock method, in order to avoid event loop
recursion which is incompatible with asyncio.
X-Gentoo-bug: 614108
X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=614108
---
pym/_emerge/AsynchronousLock.py | 89 +--
Hi,
so one big swath of EAPI 0 ebuilds sits in app-xemacs/. The current
eclass, xemacs-packages.eclass is from days gone by and does little in
terms of modern eclass/ebuild best-practices. I have rewritten it, and
with it will port all ebuilds to it and EAPI 6 (which can be automated,
due to the
