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

netbsd: Adapt to BSD-common infra changes for FreeBSD #194698

Merged
merged 3 commits into from
Oct 6, 2022

Conversation

Ericson2314
Copy link
Member

@Ericson2314 Ericson2314 commented Oct 6, 2022

Description of changes

See #82131 for the rest of the changes for FreeBSD. This is PRed separately because it is a macOS moderate rebuild so we target staging.

The main change is that we CD to the path we're building after applying patches, so we can patch other parts of the tree (from extraPaths) as needed.

Another change is that netbsd.install no longer depends on fts, which it evidently no longer needs.

Also, rename BSD_PATH to COMPONENT_PATH .

Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • 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/)
  • 22.11 Release Notes (or backporting 22.05 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
    • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
  • Fits CONTRIBUTING.md.

@ofborg ofborg bot added the 6.topic: bsd Running or building packages on BSD label Oct 6, 2022
@Ericson2314 Ericson2314 changed the base branch from master to staging October 6, 2022 04:57
Copy link
Member

@alyssais alyssais left a comment

Choose a reason for hiding this comment

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

Approach makes sense.

So BSD_PATH is the path of the component we're building? Can we call it something less confusing?

pkgs/os-specific/bsd/netbsd/default.nix Outdated Show resolved Hide resolved
mkdir -p $(dirname $last)
xinstall "$@"
@out@/bin/xinstall "$@"
Copy link
Member

Choose a reason for hiding this comment

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

Is this just because it's more correct, or did something break?

Copy link
Member Author

Choose a reason for hiding this comment

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

@alyssais just more correct for NetBSD, but when I went to build FreeBSD Make with NetBSD Make or something like that it did break.

@Ericson2314
Copy link
Member Author

BSD_PATH was the name it was already using, but I am happy to change it.

@alyssais
Copy link
Member

alyssais commented Oct 6, 2022

BSD_PATH was the name it was already using, but I am happy to change it.

Yeah, I saw that you didn't introduce it. I think it would be worth changing though, as I assumed it would refer to the root directory, which made seeing how the change worked quite confusing.

See NixOS#82131 for the rest of the
changes for FreeBSD. This is PRed separately because it is a macOS
moderate rebuild so we target staging.

The main change is that we CD to the path we're building *after*
applying patches, so we can patch other parts of the tree (from
`extraPaths`) as needed.

Another change is that `netbsd.install` no longer depends on `fts`,
which it evidently no longer needs.
@alyssais and I agreed this is clearer.
@Ericson2314 Ericson2314 merged commit 9a5fa3b into NixOS:staging Oct 6, 2022
@Ericson2314 Ericson2314 deleted the freebsd-prep branch October 6, 2022 20:17
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.

2 participants