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
standardnotes: init at 2.3.12 #49370
Conversation
c3d5589
to
5f5f974
Compare
Thank you for you reviews. It should be all good now! If it is, I'll fixup all my commit into one. |
Branch is rebased, everything should be in order 👍 |
Unexpected error: command failed with exit code 1 on x86_64-linux (full log) Attempted: standardnotes Partial log (click to expand)
|
Hash mismatch |
Thank you for your answer. The release page of standardnotes offers multiple files in the release. By default, Anyway, is there a way to specify which file to download from the release with Thank you for your help EDIT: I will edit my package so It compiles standardnotes from source but I'm still interested of knowing whether It's actually possible to specify a file to |
@GrahamcOfBorg build standardnotes |
@dywedir I've been trying to build standardnotes from source but haven't been able to, mostly because this is an electron app. It might be possible to do so but as I'm not experienced enough with nixpkgs at the moment. In the meanwhile, I'm using the AppImage from the official release and this is working perfectly 👍 Thank to all participant who took the time to look at this PR. |
There is precedent for not building electron apps but using the binary
instead, see VSCode and Atom.
…On Fri, 9 Nov 2018, 11:27 Grégoire Martinache, ***@***.***> wrote:
@dywedir <https://github.com/dywedir> I've been trying to build
standardnotes from source but haven't been able to, mostly because this is
an electron app. It might be possible to do so but as I'm not experienced
enough with nixpkgs at the moment.
In the meanwhile, I'm using the AppImage from the official release and
this is working perfectly 👍
I believe this is not a problem but feel free to tell me otherwise.
Thank to all participant who took the time to look at this PR.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#49370 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGv3p3zUBui9ZLVrd_y3dhqQqPuXGGoGks5utViFgaJpZM4X-Mnv>
.
|
@M-Gregoire thank you! I'll make some changes, if you don't mind |
Sure, go ahead! |
Whoops, wrong branch, reopened at #50069 |
The appimageTools attrset contains utilities to prevent the usage of appimage-run to package AppImages, like done/attempted in NixOS#49370 and NixOS#53156. This has the advantage of allowing for per-package environment changes, and extracts into the store instead of the users home directory. The package list was extracted into appimageTools to prevent duplication.
The appimageTools attrset contains utilities to prevent the usage of appimage-run to package AppImages, like done/attempted in NixOS#49370 and NixOS#53156. This has the advantage of allowing for per-package environment changes, and extracts into the store instead of the users home directory. The package list was extracted into appimageTools to prevent duplication.
Motivation for this change
Add standardnotes to nixpkgs.
Please note this is my first time doing a derivation, any review is welcome.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)