-
-
Notifications
You must be signed in to change notification settings - Fork 17.8k
_86BoxManagerX: init at 1.7.6.0-e #307611
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
Conversation
51e7863 to
dfa57fd
Compare
|
Changelog from 4aae8545d2aa651461708e2e702ac5a9831e43f0 to faab013b3ec3e4de810995a82066afbbab91a2f6:
Changelog from faab013b3ec3e4de810995a82066afbbab91a2f6 to 51e7863ebab0893253559e55f49235cd1300565f:
Changelog from 51e7863ebab0893253559e55f49235cd1300565f to dfa57fdde5deb1bc59a350d0cb3a2eda75af2179:
|
dfa57fd to
2b0bb70
Compare
| dotnet-sdk = dotnetCorePackages.sdk_6_0; | ||
| dotnet-runtime = dotnetCorePackages.runtime_6_0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.NET 6 will be removed #326335
|
Welp, I should not have neglected this PR so much. Sorry. 86Box 5.0 comes with a builtin VM manager, and while I'm not sure that makes 86BoxManagerX fully obsolete by any means, it does somewhat obviate the need for this, and therefore I would prefer to not add the maintenance burden of adding another external manager to Nixpkgs. If anyone still wants to pick this up, please feel free to take over where I left off. |
Description of changes
https://github.com/RetBox/86BoxManagerX
86BoxManagerX is a cross-platform fork of 86BoxManager, a configuration manager for 86Box. 86BoxManagerX makes it easy to manage multiple different machine configurations using 86Box.
In order to integrate it well into Nixpkgs, the following patches were made:
$XDG_CONFIG_HOMErather than the directory of the assembly, which would point into the read-only Nix store. This is adapted from a pending pull request.The justification for this is a result of the way 86BoxManagerX works: at first startup, it creates the configuration files after detecting the path to 86Box, and encodes the path to 86Box into the configuration file. After this, it does not try to find the 86Box executable again, even if it stops existing. It would be nice if the configuration could override the hardcoded path, but that'd be a much more involved patch, whereas this one is almost entirely just removing things, which should be easy to deal with. Adding upstream support for the hardcoded path might make this easier in the future.
P.S.: The reason the
versionstring differs from the tag in having an additional hyphen is becausebuildDotnetModuledisallows the string1.7.6.0e.Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.