-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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
fish: 3.1.0 -> 3.1.1 #86136
fish: 3.1.0 -> 3.1.1 #86136
Conversation
fish-shell/fish-shell@3.1.0...3.1.1 The patch we had to use for Apple SDKs was merged upstream, so it can be dropped. I ran nixpkgs-fmt, and removed the `with stdenv.lib;` scope expander. Additionally, did a little bit of cleanup. I plan on refactoring this more down the line, but this'll do for now. I finally figured out why we use `fetchurl` for the tagged release: the published release tarballs contain a version file, which the `build_tools/git_version_gen.sh` script reads (and uses as the version if it exists). The other thing it contains are pre-generated docs for various `fish` builtins. I've expanded the comment to document this so nobody is as confused as I was when I first saw it. (Though I plan to change this and add sphinx as a native build input in order to build the docs ourselves.)
@GrahamcOfBorg build fish |
Build fails on macOS due to fish-shell/fish-shell@d0a67e3:
Since we presumably don't want to break the sandbox just for codesigning (can you even Ad-Hoc codesign without a developer account?) we're going to have to disable it. I'll file an upstream issue about having an official way to turn it off, but until then I guess we can just patch |
Upstream issue filed as fish-shell/fish-shell#6952. |
We don't have access to the codesign binary.
Looks like the code signing was patched out :) |
Do you want to add yourself as a maintainer? |
The |
There's now a way on fish master to disable it: fish-shell/fish-shell@3a47db7 So we can set that new value on the next release. |
Merged #86136 into master.
Would have liked to see the test added first, but maybe somebody can
do that as a followup.
…On Tue, Apr 28, 2020 at 7:55 PM Lily Ballard ***@***.***> wrote:
There's now a way on fish master to disable it: ***@***.***
So we can set that new value on the next release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The only reason the test wasn't added was because it fails. I've been working off and on to try and fix it up, but the tempfile appears to never get created: EDIT: That was easy. Just had to look at the docs for |
Test fixed in followup here: #86802. |
Great, thanks
…On Mon, May 4, 2020 at 7:19 PM Cole Helbling ***@***.***> wrote:
Test fixed in followup here: #86802
<#86802>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#86136 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYB5ZSTN4JHOVYQB4OQCZTRP32I5ANCNFSM4MSC4YOQ>
.
|
fish-shell/fish-shell@3.1.0...3.1.1
The patch we had to use for Apple SDKs was merged upstream, so it can be
dropped. I ran nixpkgs-fmt, and removed the
with stdenv.lib;
scopeexpander.
Additionally, did a little bit of cleanup. I plan on refactoring this
more down the line, but this'll do for now.
I finally figured out why we use
fetchurl
for the tagged release: thepublished release tarballs contain a version file, which the
build_tools/git_version_gen.sh
script reads (and uses as the versionif it exists). The other thing it contains are pre-generated docs for
various
fish
builtins. I've expanded the comment to document this sonobody is as confused as I was when I first saw it. (Though I plan to
change this and add sphinx as a native build input in order to build the
docs ourselves.)
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)cc @lilyball: Mind testing on macOS, to ensure we don't run into a similar issue to last time?
cc @Profpatsch: Is the
withTests
stuff still necessary? Can I drop it, or is there something you'd like done with it?EDIT: I also verified that the NixOS module's patch still applies, but if somebody could determine for certain whether or not anything needs to be fixed there, as well, I'd appreciate it.