Gentoo Packages

Search

Install

Install this package:

emerge -a dev-python/nvidia-cudnn-frontend

Package Information

Description:

cuDNN Frontend Python bindings (header API + nanobind layer)

Homepage:

https://github.com/NVIDIA/cudnn-frontend https://pypi.org/project/nvidia-cudnn-frontend/

License:

Apache-2.0 MIT

Versions

Metadata

Maintainers

• Ivan S. Titov (iohann.s.titov@gmail.com) - Type: person

Upstream

• Bugs: https://github.com/NVIDIA/cudnn-frontend/issues
• Remote IDs:
  • pypi: nvidia-cudnn-frontend
  • github: NVIDIA/cudnn-frontend

<pkgmetadata>
	<maintainer type="person">
		<email>iohann.s.titov@gmail.com</email>
		<name>Ivan S. Titov</name>
	</maintainer>
	<upstream>
		<bugs-to>https://github.com/NVIDIA/cudnn-frontend/issues</bugs-to>
		<remote-id type="pypi">nvidia-cudnn-frontend</remote-id>
		<remote-id type="github">NVIDIA/cudnn-frontend</remote-id>
	</upstream>
</pkgmetadata>

Lint Warnings

• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• [Notice] Package has only unstable keywords for arch(es): [ amd64 ], all versions are unstable: [ 1.31.0, 1.32.0, 1.32.1 ]

Manifest