New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kodiPlugins: add YATP, drop exodus #46403
Conversation
Success on x86_64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
The mass rebuild seems to by caused by dropping the split outputs of |
The mass rebuild seems to by caused by dropping the split outputs of `pythonPackages.requests`.
Is that really necessary to build the `kodi` plugins?
Hm. Looking at this with a fresh eye I now think I misunderstood what empty "dev" output of `pythonPackages.requests` on `master` did. It contains `nix-support/propagated-build-inputs` file, which now makes sense to me.
Removed that patch and fixed `yatp` expression instead. This should now go to `master`, as it no longer a mass rebuild.
But don't merge yet, I want to test this revision too.
|
Success on x86_64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
Yes, the |
Success on aarch64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
@oxij is this ready to merge now? |
Nope, unfortunately YATP doesn't start with multiple-output `requests`. :(
I'll investigate later this week.
|
The `dev` output is empty anyway. The problem is that it interacts badly with other parts of python and stdenv infrastructure. In particular, before this patch it installs code into `out` output (with only generated `nix-support` in `dev`), but `makePythonPath` then uses `propagatedBuildInputs` to generate `PYTHONPATH` while stdenv selects `dev` outputs for `propagatedBuiltInputs`. This results in `makePythonPath` linking to the empty `dev` output in `PYTHONPATH`. This reverts a piece of commit 28299f6.
No loner exists, I couldn't find an official replacement repo, should be removed according to NixOS#46196 (comment)
Success on aarch64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
After digging through the internals I came to the conclusion that the original approach was correct. See the commit messages. I think this need some more input from @FRidh. |
Success on x86_64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
Btw, after digging this I now feel like going through all multi-output python packages and removing multiple outputs from those that have |
Yes, we should remove multiple outputs in case of Python packages because it doesn't work. As soon as an output is defined, the The original idea was to get certain build-time dependencies out of a closure if I understood correctly, but that seems to have been resolved elsewhere already. |
So this should be good to merge to staging then, is it not?
|
Note I suggest that Kodi packages are going to be put in a file of their own. That gives the possibility to use @r-ryantm |
Success on x86_64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: kodiPlugins.simpleplugin, kodiPlugins.yatp Partial log (click to expand)
|
I see, I'll keep that in mind.
Anyway. Thanks!
|
Motivation for this change
Continuation of #46196. A mass rebuild.
Things done
Note: after adding
yatp
intokodiWithPlugins
you have to enable YATP manually in Kodi UI.Merge at will.