Package naming conventions: Difference between revisions

From NixOS Wiki
Patka (talk | contribs)
Fleshed out the bin and unwrapped suffix. wrapped doesn't exist and is removed. still and fresh are exlusively libreoffice upstream names so have also been removed.
Patka (talk | contribs)
m Correctly close code tag
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
! Use
! Use
|-
|-
| -bin
| <code>-bin</code>
|The binary is copied from upstream, not build from source using Nix. A -bin version is only available if a source-based version already exists, and there exists a meaninful difference between the two. An example is the Hashicorp Vault package that doesn't include the web UI, but the -bin version does.
|The binary is copied from upstream, not build from source using Nix. A <code>-bin</code> version is only available if a source-based version already exists, and there exists a meaninful difference between the two. An example is the Hashicorp Vault package that doesn't include the web UI, but the <code>-bin</code> version does.
|-
|-
| -unwrapped
| <code>-unwrapped</code>
|Some packages provide options for customization that don't affect the main build, and is thus done in the -unwrapped package. The package is then wrapped to provide customization without having to recompile the package. This is an implementation detail, you generally don't want to directly use an -unwrapped version.
|Some packages provide options for customization that don't affect the main build, and is thus done in the <code>-unwrapped</code> package. The package is then wrapped to provide customization without having to recompile the package. This is an implementation detail, you generally don't want to directly use an <code>-unwrapped</code> version.
|}
|}

Latest revision as of 19:02, 8 April 2024

When looking through the available Nix packages, one might find some naming conventions.

Suffix Use
-bin The binary is copied from upstream, not build from source using Nix. A -bin version is only available if a source-based version already exists, and there exists a meaninful difference between the two. An example is the Hashicorp Vault package that doesn't include the web UI, but the -bin version does.
-unwrapped Some packages provide options for customization that don't affect the main build, and is thus done in the -unwrapped package. The package is then wrapped to provide customization without having to recompile the package. This is an implementation detail, you generally don't want to directly use an -unwrapped version.