Prashant Rahul commented on a discussion on README.md: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/218#note_143235 > podman rmi rtems-docs-server_img > ``` > > +### NixOS > + > +Create a `shell.nix` file with the folllowing content: > +```nix > +{ }: > +let > + pkgs = > + import > + (fetchTarball > "https://github.com/NixOS/nixpkgs/archive/aa290c9891fa4ebe88f8889e59633d20cc06a5f2.tar.gz";) Ya, firstly, the `py-markdown-table` package is not present in any of the stable channels of [nixpkgs](https://github.com/nixos/nixpkgs) as of right now. However, it is present in the master channel. The hash you see in the url is a commit hash taken from master branch of nixpkgs. Instead of hash one could use a branch url, something like: `https://github.com/nixos/nixpkgs/archive/refs/heads/master.tar.gz` or even a stable release: `https://github.com/nixos/nixpkgs/archive/refs/tags/25.11.tar.gz` The problem is that this will download and evaluate entire nixpkgs tarball (around 50MB) everytime you enter the dev shell (which is basically everytime you open a new shell and want to compile the docs) However we can pin to a specific commit hash, This will download and evalute nixpkgs only once and cache it since the remote won't change. Also, I am certain that `py-markdown-table` will be in the `26.05` stable release. When that's done, the commit hash can be changed to any commit hash in the `26.05` branch, preferably the latest one. And in the future afterwards, any commit hash from the stable branch will work, assuming no new packages is required which may not be present in that commit. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/218#note_143235 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
