python3Packages.rio-stac: init at 0.10.1

[daspk04]

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[ethancedwards8]

does this even do anything? This is a library not a program...

[daspk04]

Thanks @ethancedwards8 !

I think I missed to add a mainProgram. Technically this can also be used as a cli. c.f, c.f

However it seems like when I build it, it doesn't generate any file inside bin folder. Ideally this should be there.

Anyways I will remove it.

[daspk04]

I have removed it

[GaetanLepage]

It is indeed a CLI, so you should add meta.mainProgram and versionCheckHook if possible.

Also, add a pkgs/by-name/ri/rio-stac/package.nix containing:

{ python3Packages }: with python3Packages; toPythonApplication rio-stac

[GaetanLepage]

(merge conflict too)

[daspk04]

It is indeed a CLI, so you should add meta.mainProgram and versionCheckHook if possible.

Also, add a pkgs/by-name/ri/rio-stac/package.nix containing:

{ python3Packages }: with python3Packages; toPythonApplication rio-stac

Thanks @GaetanLepage !

But the when I built this locally, I found no bin folder being generated. So I'm actually not sure what is the issue. So I didn't add it. earlier comment

[GaetanLepage]

It is indeed a CLI, so you should add meta.mainProgram and versionCheckHook if possible.
Also, add a pkgs/by-name/ri/rio-stac/package.nix containing:

{ python3Packages }: with python3Packages; toPythonApplication rio-stac

Thanks @GaetanLepage !

But the when I built this locally, I found no bin folder being generated. So I'm actually not sure what is the issue. So I didn't add it. earlier comment

Maybe it's a packaging issue on their end then... It's fine to package only the library for now. But it would be better to at least open an issue upstream.

[GaetanLepage]

If you's not willing to open an issue, maybe simply leave a comment in the file stating that it should provide a program but that nothing is installed in $out/bin.

[daspk04]

Maybe it's a packaging issue on their end then... It's fine to package only the library for now. But it would be better to at least open an issue upstream.

Thanks @GaetanLepage !

I have added a comment in the file. For now I'm not opening an issue upstream.

[GaetanLepage]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 392056

---

x86_64-linux

✅ 4 packages built:

• python312Packages.rio-stac
• python312Packages.rio-stac.dist
• python313Packages.rio-stac
• python313Packages.rio-stac.dist

---

aarch64-linux

✅ 4 packages built:

• python312Packages.rio-stac
• python312Packages.rio-stac.dist
• python313Packages.rio-stac
• python313Packages.rio-stac.dist

---

x86_64-darwin

✅ 4 packages built:

• python312Packages.rio-stac
• python312Packages.rio-stac.dist
• python313Packages.rio-stac
• python313Packages.rio-stac.dist

---

aarch64-darwin

✅ 4 packages built:

• python312Packages.rio-stac
• python312Packages.rio-stac.dist
• python313Packages.rio-stac
• python313Packages.rio-stac.dist