Code change:
Steps to reproduce the behavior: Attempt to build vmware-workstation from the unstable branch using the following command: sudo nixos-rebuild switch --flake ~/nixos#framework --show-trace Observe the build failure with the following error related to the --docdir option in the configure flags. Build log Running phase: updateAutotoolsGnuConfigScriptsPhase Updating Autotools / GNU config script to a newer upstream version: Updating Autotools / GNU config script to a newer upstream version: Running phase: configurePhase fixing libtool script patching script interpreter paths in ./configure ./configure: interpreter directive changed from "#! /bin/sh" to "/nix/store/4bj2kxdm1462fzcc2i2s4dn33g2angcc-bash-5.2p32/bin/sh" configure flags: --disable-static --prefix=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3 --bindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/bin --sbindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/sbin --includedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --oldincludedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --mandir=/nix/store/64jmdcjmdl94l4hbadwqsz7j8qg16dwb-gdbm-1.8.3-man/share/man --infodir=/nix/store/vs7bglvjl3pxp2ffc98v5w7xlinn0q5j-gdbm-1.8.3-info/share/info --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm --libdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/lib --libexecdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/libexec --localedir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/share/locale --enable-libgdbm-compat configure: error: unrecognized option: --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm Try `./configure --help' for more information. Additional context I tried building the package on NixOS 24.05 with the following command, and the build succeeded without any issues: Notify maintainers cc Metadata [user nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Please update the issue's title with the actual package name ()
do we really need specific gdbm version during the build? or as a buildInputs?
I removed the override from and I can build and run vmware just fine. Could you just update the dependency version to 1.24 and remove the install override?
How can I do it myself? Download and edit the nixpkg and edit it?
Sorry, I didn't mean "you" as in you specifically, but more generally as a third person pronoun. I don't know how either, never contributed to nixpkgs before . I meant for the question to be at nixpkgs contributors to know if what I proposed makes sense. EDIT: Oh, might have misunderstood you. If you want to do the same thing I did then yes, get a local clone of nixpkgs, edit the file and point your system nixpkgs to the local clone. Here's the patch that worked for me: <details<summaryClick to show patch </summary</detailsNote that it doesn't pin the version of gdbm, it will always use the latest version from nixpkgs which may cause with future versions. I'm assuming there was a reason the original was pinned to 1.8.3.
Thanks it's very informative!

Related discussion:
text: sha256 = "sha256-JSEW1gqQuLGRkathlwZU/TnG6dL/xWKW4//SfE+kO0A="; }; <del> gdbm3 = gdbm.overrideAttrs (old: rec { version = "1.8.3"; src = fetchurl { url = "mirror://gnu/gdbm/gdbm-${version}.tar.gz"; sha256 = "sha256-zDQDOKLii0AFirnrU1SiHVP4ihWC6iG6C7GFw3ooHck="; }; installPhase = '' mkdir -p $out/lib cp .libs/libgdbm*.so* $out/lib/ ''; }); </del> vmware-unpack-env = buildFHSEnv rec { name = "vmware-unpack-env"; targetPkgs = pkgs: [ zlib ];