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
WIP: dracut: init at 049 #77868
WIP: dracut: init at 049 #77868
Conversation
Also is running |
If somebody knows more how to package this better, please recommend. |
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.
No idea if wrapProgram
is intended to be used like that.
}: | ||
|
||
stdenv.mkDerivation rec { | ||
name = "dracut"; |
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.
why name and not pname?
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.
pname
is just name right and then combined with version
right?
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.
Usually pname
is preferred and if that's used without name
, mkDerivation
and all it's friends create automatically this attribute: name = "${pname}-${version};"
- this name
is different then yours.
stdenv.mkDerivation rec { | ||
name = "dracut"; | ||
version = "049"; | ||
src = fetchurl { |
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.
Is there a reason why you didn't use fetchFromGitHub?
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.
Does that fetch the releases?
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.
@ajs124 is right @CMCDragonkai - We prefer fetchFromGitHub
since it's easier to parse our package set that way and it's easier to override the revision (rev
) with the \\
operator. Plus, it might be useful in the future when automatic updaters scripts will see that instead of the too generic fetchurl
.
Does fetchFromGithub get releases? I forgot.
Any alternative to setting the PATH for all the scripts?
…On 19 January 2020 08:29:05 GMT+11:00, ajs124 ***@***.***> wrote:
ajs124 requested changes on this pull request.
No idea if `wrapProgram` is intended to be used like that.
> +, utillinux
+, gnused
+, gnugrep
+, squashfsTools
+, cpio
+, binutils
+, gzip
+, bzip2
+, lz4
+, lzop
+, zstd
+, xz
+}:
+
+stdenv.mkDerivation rec {
+ name = "dracut";
why name and not pname?
> +, gnugrep
+, squashfsTools
+, cpio
+, binutils
+, gzip
+, bzip2
+, lz4
+, lzop
+, zstd
+, xz
+}:
+
+stdenv.mkDerivation rec {
+ name = "dracut";
+ version = "049";
+ src = fetchurl {
Is there a reason why you didn't use fetchFromGitHub?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#77868 (review)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
}: | ||
|
||
stdenv.mkDerivation rec { | ||
name = "dracut"; |
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.
Usually pname
is preferred and if that's used without name
, mkDerivation
and all it's friends create automatically this attribute: name = "${pname}-${version};"
- this name
is different then yours.
stdenv.mkDerivation rec { | ||
name = "dracut"; | ||
version = "049"; | ||
src = fetchurl { |
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.
@ajs124 is right @CMCDragonkai - We prefer fetchFromGitHub
since it's easier to parse our package set that way and it's easier to override the revision (rev
) with the \\
operator. Plus, it might be useful in the future when automatic updaters scripts will see that instead of the too generic fetchurl
.
--replace 'dracutbasedir=/usr/lib/dracut' "dracutbasedir=$out/lib/dracut" | ||
''; | ||
postFixup = '' | ||
wrapProgram $out/bin/dracut --set PATH ${lib.makeBinPath [ |
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.
No idea if wrapProgram is intended to be used like that.
@ajs124 I think it's supposed to be OK, see https://nixos.org/nixpkgs/manual/#ssec-stdenv-functions .
substituteInPlace lsinitrd.sh \ | ||
--replace 'dracutbasedir=/usr/lib/dracut' "dracutbasedir=$out/lib/dracut" | ||
''; | ||
postFixup = '' |
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.
Any alternative to setting the PATH for all the scripts?
I think @CMCDragonkai you can do something like this (not tested):
postFixup = '' | |
# put here all the packages you need - wrap them all | |
wrapPATH = lib.makeBinPath [ ... ]; | |
postFixup = '' | |
wrapProgram $out/bin/dracut --set PATH ${wrapPATH} | |
''; |
BUT, TBH I'm a bit conflicted whether all of those packages are needed as they are expected to be available in almost every environment. Personally, I'd drop at least:
gzip
bzip2
xz
gnugrep
gnused
BTW I assume makeBinPath
uses the order of the packages it gets in order to give precedence in $PATH
. Hence, If upstream requires explicitly gnused
instead whatever's in coreutils
, you should put gnused
before coreutils
.
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.
I think the derivation should be as pure as possible to ensure that if I package dracut
in a docker container it should have everything.
Hello, I'm a bot and I thank you in the name of the community for your contributions. Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do: If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list. If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past. If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments. Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel. |
I marked this as stale due to inactivity. → More info |
Co-authored-by: Doron Behar <doron.behar@gmail.com>
I marked this as stale due to inactivity. → More info |
I've continued this PR in #210075 |
Motivation for this change
Fixes #77858
This derivation still has some problems. In particular
realpath
is not found in the dracut command. And also thedracutbasedir
has shell scripts there that have not been properly wrapped as well. And also I need to wrap the bin scripts with a PATH to itself, but not sure if that means I need to add$out
to thelib.makeBinPath
.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)