Navigation Menu

Skip to content
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

[WIP] Refactor libprefixed packages to multioutput #38494

Closed
wants to merge 5 commits into from

Conversation

avnik
Copy link
Contributor

@avnik avnik commented Apr 6, 2018

Motivation for this change

Say "farewell" to long-lived ad-hoc hack, when we had two derivations for one package -- one for library-only version, second one with server/utils built.

See #14693 for problem history and details.

Done (Minimum to be done)

Not sure about this two, my expertise can be not enough. If I fail to refactor them, I'll create separate issues

  • [ ] krb5

At least volunters for testing would be needed, I haven't any ffado compatible hardware, and can test stuff only for "just executed and shows version". Also I can't check darwin build myself.

I am sure, that is a mass-rebuild, so eventually this PR will be altered to be against staging. One of reasons, why I open PR early -- is prevend duplications of work, and use ofborg to look how much stuff affected.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

We can't say final farewell for it, due ffado-mixer, which give us
nice build-loop, so postpone it until I (or someone other) write
separate derivation for mixer-only (because is just python script,
with dependencies in PyQT/PyDbus)
@matthewbauer
Copy link
Member

Hi! Thanks for doing this. I opened a similar PR in #39683 but you seem to have gotten further along. A few more that (maybe) can be removed:

  • libv4l
  • poppler_utils

optAlsaLib = shouldUsePkg alsaLib;
# Mixer/tools dependencies
# FIXME: can we build mixer separately? Then we can farewell `libOnly` mode
# (otherwise we have perfect loop via qt -> pulseaudio -> jack -> ffado -> qt)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can probably override ffado in jack's callPackage-jack shouldn't need Qt.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ffado' mixer is actually separate app, which have completely own dependencies (dbus-python and PyQt), so I feel separate expression may be better solution. But would be nice to hear someone who use ffado.

optPythonDBus = if libOnly then null else shouldUsePkg dbus-python;
optLibffado = if libOnly then null else shouldUsePkg libffado;
optAlsaLib = if libOnly then null else shouldUsePkg alsaLib;
optPythonDBus = shouldUsePkg dbus-python;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can probably get rid of shouldUsePkg. I think they are officially deprecated (just use dbus-python directly).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It don't used outside of mixer, so if we move mixer to own app, we can drop dbus-python in main ffado.

@oxij
Copy link
Member

oxij commented May 1, 2018 via email

@avnik
Copy link
Contributor Author

avnik commented May 1, 2018

@oxij libOnly here is definelly not use-flag.

Other question to all -- I had intention to split daemon part of pulseaudio from client binaries (to daemon and bin outputs respectively) -- does it a good idea, or too radical? Then we can drop some useflags from pulseaudio -- extra dependencies (like jack/ffado) needed only for daemon, but not for client utilities like pactl/pacmd/....

@avnik
Copy link
Contributor Author

avnik commented Jun 20, 2018

Some work, which already done kicked to own PRs, just updated this issue to keep progress tracking (still use it as WIP branch)

@mmahut
Copy link
Member

mmahut commented Aug 3, 2019

What is the status of this pull request?

@avnik
Copy link
Contributor Author

avnik commented Aug 5, 2019

@mmahut ffado and heimdal done and merged. Pulseaudio still pending, I'll try to rebase my patches and push them to own PR, also I feel worth to migrate pulseaudio package to using meson, instead autoconf.

@stale
Copy link

stale bot commented Jun 1, 2020

Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the
    related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse. 3. Ask on the #nixos channel on
    irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 1, 2020
@avnik
Copy link
Contributor Author

avnik commented Jun 5, 2020

Actually only pulseaudio refactoring pending, so I can close it

@avnik avnik closed this Jun 5, 2020
@avnik avnik deleted the refactor/libprefixed-to-multioutput branch June 5, 2020 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants