Package naming conventions - Revision history

Pigs: Add category nixpkgs

2025-05-18T18:38:54Z

Add category nixpkgs

← Older revision		Revision as of 18:38, 18 May 2025
Line 11:		Line 11:
	\|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.		\|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.
	\|}		\|}

			[[Category:Nixpkgs]]

Patka: Correctly close code tag

2024-04-08T19:02:49Z

Correctly close code tag

← Older revision		Revision as of 19:02, 8 April 2024
Line 5:		Line 5:
	! Use		! Use
	\|-		\|-
	\| <code>-bin<code>		\| <code>-bin</code>
	\|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.		\|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.
	\|-		\|-

Patka: Add `tags`


2024-04-08T13:35:42Z
Add <code> tags

				
				
				
				
				
				← Older revision
				Revision as of 13:35, 8 April 2024
				
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.
|} |}



Patka: 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.
2024-04-08T13:30:39Z
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.

				
				
				
				
				
				← Older revision
				Revision as of 13:30, 8 April 2024
				
Line 1:
Line 1:
An attempt to document the unofficial naming conventions used for packages in the nixpkgs repository When looking through the available Nix packages, one might find some naming conventions.
  {| class="wikitable"
{| class="wikitable"   
|- |-
! Suffix ! Suffix
Line 7:
Line 6:
|- |-
| -bin | -bin
| Binaries that aren't compiled by nix |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.
|- 
| -fresh 
| 
|- 
| -still 
| 
|- 
| -wrapped 
| Provides configuration options to the -unwrapped derivation 
|- |-
| -unwrapped | -unwrapped
| Indicator that there is a wrapped version |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.
|} |}

<!-- Tabe generated with https://www.tablesgenerator.com/mediawiki_tables --> 





imported>MichaelCTS: note how table was generated
2023-07-19T08:18:36Z
note how table was generated

				
				
				
				
				
				← Older revision
				Revision as of 08:18, 19 July 2023
				
Line 21:
Line 21:
| Indicator that there is a wrapped version | Indicator that there is a wrapped version
|} |}

<!-- Tabe generated with https://www.tablesgenerator.com/mediawiki_tables -->





imported>MichaelCTS: Init the page
2023-07-19T08:15:49Z
Init the page
New page
An attempt to document the unofficial naming conventions used for packages in the nixpkgs repository



{| class="wikitable" 

|-

! Suffix

! Use

|-

| -bin

| Binaries that aren't compiled by nix

|-

| -fresh

| 

|-

| -still

| 

|-

| -wrapped

| Provides configuration options to the -unwrapped derivation

|-

| -unwrapped

| Indicator that there is a wrapped version

|}

← Older revision		Revision as of 13:35, 8 April 2024
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.
	\|}		\|}

← Older revision		Revision as of 13:30, 8 April 2024
Line 1:		Line 1:
	~~An attempt to document~~ the ~~unofficial~~ naming conventions ~~used for packages in the nixpkgs repository~~		When looking through the available Nix packages, one might find some naming conventions.
			{\| class="wikitable"
	{\| class="wikitable"
	\|-		\|-
	! Suffix		! Suffix
Line 7:		Line 6:
	\|-		\|-
	\| -bin		\| -bin
	\| ~~Binaries~~ that ~~aren~~'t ~~compiled by nix~~		\|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.
	\|-
	~~\| -fresh~~
	\|
	\|-
	~~\| -still~~
	\|
	\|-
	~~\| -wrapped~~
	~~\| Provides configuration options to~~ the -~~unwrapped derivation~~
	\|-		\|-
	\| -unwrapped		\| -unwrapped
	\| ~~Indicator~~ that ~~there~~ is a wrapped version		\|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.
	\|}		\|}

	~~<!-- Tabe generated with https://www.tablesgenerator.com/mediawiki_tables -->~~

← Older revision		Revision as of 08:18, 19 July 2023
Line 21:		Line 21:
	\| Indicator that there is a wrapped version		\| Indicator that there is a wrapped version
	\|}		\|}

			<!-- Tabe generated with https://www.tablesgenerator.com/mediawiki_tables -->

Package naming conventions - Revision history

Pigs: Add category nixpkgs

Patka: Correctly close code tag

Patka: Add tags

Patka: 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.

imported>MichaelCTS: note how table was generated

imported>MichaelCTS: Init the page

Patka: Add `tags`