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

rPackages.FLAMES: fix build #303210

Merged
merged 1 commit into from
Apr 12, 2024
Merged

rPackages.FLAMES: fix build #303210

merged 1 commit into from
Apr 12, 2024

Conversation

Kupac
Copy link
Contributor

@Kupac Kupac commented Apr 10, 2024

Description of changes

Added missing sysdeps and patched out code that tried to reduce library size by stripping symbols/
It fixes build, but the package doesn't function yet. it uses basilisk, which tries to install miniconda, but this won't run on nixos. basilisk should be patched/fixed to use another python env, if possible at all

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

@Kupac Kupac requested a review from jbedo as a code owner April 10, 2024 21:03
@superherointj
Copy link
Contributor

Why package name is in uppercase? Shouldn't it be lowercase? What are the consequences of having it in lowercase?

@jbedo
Copy link
Contributor

jbedo commented Apr 10, 2024

Why package name is in uppercase? Shouldn't it be lowercase? What are the consequences of having it in lowercase?

It's uppercase because that's how it's registered in CRAN. Renaming CRAN packages would lead to a lot of confusion and difficulty.

@jbedo
Copy link
Contributor

jbedo commented Apr 10, 2024

@ofborg build rPackages.FLAMES

@b-rodrigues
Copy link
Contributor

Builds successfully on aarch-linux, lgtm

@superherointj superherointj merged commit 90d0d40 into NixOS:master Apr 12, 2024
25 checks passed
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.

4 participants