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

kinfocenter: create symlink manually #107781

Closed
wants to merge 1 commit into from
Closed

Conversation

peterhoeg
Copy link
Member

Motivation for this change

kinfocenter is not a standalone binary but instead a symlink to systemsettings5. However, without this PR it's just a dangling symlink as it otherwise expects systemsettings5 to exist in the same directory.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • 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 nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@SuperSandro2000
Copy link
Member

Result of nixpkgs-review pr 107781 run on x86_64-linux 1

2 packages marked as broken and skipped:
  • libsForQt512.kinfocenter
  • libsForQt514.kinfocenter
1 package built:
  • plasma5.kinfocenter (libsForQt5.kinfocenter)

fdl12 is a deprecated license, check if project uses fdl12Plus or fdl12Only and change meta.license accordingly.

@peterhoeg
Copy link
Member Author

fdl12 is a deprecated license, check if project uses fdl12Plus or fdl12Only and change meta.license accordingly.

The licenses are handled centrally for all plasma stuff, so while your comment is absolutely valid, it's separate for the purpose of this.

@hamburger1984
Copy link
Contributor

This fixes kinfocenter for me:

@SuperSandro2000
Copy link
Member

@ttuegel @jtojnar could you take a look?

@jtojnar
Copy link
Contributor

jtojnar commented Jan 12, 2021

@SuperSandro2000 whether you want to solve it by overriding the broken symlink with a correct one or patching the build script is just a matter of maintainer’s preference. I like to do the latter since patch failure will let me know when something changed but replacing a symlink is an easy fix to do and some maintainers might prefer that.

I suspect you @hamburger1984 is disabling the multiple outputs because they cannot find the binary output in out. But that is fine, we have bin output so it gets installed there. Just the patching of CMakeScripts.txt should be sufficient if you change the interpolation to ${lib.getBin systemsettings}, ${systemsettings.bin} or (using the fact that bin is first and thus the default output) just ${systemsettings}.

@SuperSandro2000
Copy link
Member

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.

Result of nixpkgs-review pr 107781 run on x86_64-linux 1

2 packages marked as broken and skipped:
  • libsForQt512.kinfocenter
  • libsForQt514.kinfocenter
2 packages failed to build and are new build failures:
  • plasma5.kinfocenter: log was empty
  • (libsForQt5.kinfocenter): log was empty

@eliasp
Copy link
Member

eliasp commented Feb 16, 2021

Duplicate of #108356 (or vice-versa), where I addressed this issue using ln -sf ${lib.getBin systemsettings}/bin/systemsettings5 $out/bin/kinfocenter in preFixup in 64e191c

@peterhoeg
Copy link
Member Author

Yours has better documentation @eliasp so let's use that instead. It's straight forward, self-contained and documented.

@peterhoeg peterhoeg closed this Feb 17, 2021
@peterhoeg peterhoeg deleted the f/kinfo branch February 17, 2021 01:13
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