GNU bug report logs -
#49123
[PATCH 0/24] Add mirage
Previous Next
Full log
Message #92 received at 49123 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Mon, 2021-06-21 at 17:53 +0200, Maxime Devos wrote:
>
> You can try to work-around the cycle
> by defining two python-plyer packages, like this
> (fill in the ...):
>
> (define-public python-plyer
> (package
> (name ...)
> (version ...)
> (build-system ...)
> ;; do not add (arguments ...) here!
> ;; (This comment should not go into the revised patch)
> (native-inputs
> ;; Add a comment on why this is necessary
> `(("python-plyer" ,python-plyer-for-tests)))
> (home-page ...)
> (synopsis ...)
> (description ...)))
>
> (define python-plyer-for-tests
> (package/hidden
> (inherit python-plyer)
> (native-inputs '())))
>
> That way, first a python-plyer without tests will be built,
> and then the real python-plyer will be built with tests.
I tried the attached patch, but it still fails with same errors when
trying to run tests. At this point I don't know if python-plyer-for-
tests is being built before or not.
Sincerely,
slg
[plyer-tests.patch (text/x-patch, attachment)]
This bug report was last modified 3 years and 326 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.