Mirroring repos - Revision history

Klinger at 20:40, 24 April 2024

2024-04-24T20:40:18Z

← Older revision		Revision as of 20:40, 24 April 2024
Line 17:		Line 17:
	<dd>This is the usual Nix requirement: a particular expression should produce the same output if it's re-run. At the bare minimum, two productions of an expression should be functionally indistinguishable, but this is a degraded case of operation.</dd>		<dd>This is the usual Nix requirement: a particular expression should produce the same output if it's re-run. At the bare minimum, two productions of an expression should be functionally indistinguishable, but this is a degraded case of operation.</dd>
	</dl>		</dl>
			[[Category:nix]]
			[[Category:Server]]

imported>Nyarly at 20:30, 3 March 2018

2018-03-03T20:30:43Z

← Older revision		Revision as of 20:30, 3 March 2018
Line 1:		Line 1:
	~~[[Category:Nixpkgs]]~~
	~~[[Category:Discussion]]~~

	Many software platforms provide their own package management tools and maintain their own public software repositories.		Many software platforms provide their own package management tools and maintain their own public software repositories.

imported>Nyarly at 18:57, 18 December 2017

2017-12-18T18:57:45Z

← Older revision		Revision as of 18:57, 18 December 2017
Line 17:		Line 17:

	<dl>		<dl>
	<dt>Reproducibility~~<\dt>~~		<dt>Reproducibility
	<dd>This is the usual Nix requirement: a particular expression should produce the same output if it's re-run. At the bare minimum, two productions of an expression should be functionally indistinguishable, but this is a degraded case of operation.</dd>		<dd>This is the usual Nix requirement: a particular expression should produce the same output if it's re-run. At the bare minimum, two productions of an expression should be functionally indistinguishable, but this is a degraded case of operation.</dd>
	</dl>		</dl>

imported>Nyarly at 18:57, 18 December 2017

2017-12-18T18:57:28Z

← Older revision		Revision as of 18:57, 18 December 2017
Line 7:		Line 7:

	This is a challenge for Nixpkgs, because Nix needs to adapt the conventions of these foreign systems to its own.		This is a challenge for Nixpkgs, because Nix needs to adapt the conventions of these foreign systems to its own.

			It's preferable for a particular foreign repository to be adapted in one way.

			There are also general best practices we'd like to promote in the development of these adapters.

			Ideally, a new contributor should be able to consult the Nixpkgs manual regarding their language, and be able to determine precisely what they need to do to add their package in a consistent way.

			<h2>Goals for Adapters</h2>

			<dl>
			<dt>Reproducibility<\dt>
			<dd>This is the usual Nix requirement: a particular expression should produce the same output if it's re-run. At the bare minimum, two productions of an expression should be functionally indistinguishable, but this is a degraded case of operation.</dd>
			</dl>

imported>Nyarly: Created page with "Category:Nixpkgs Category:Discussion Many software platforms provide their own package management tools and maintain their own public software repositories. This is..."

2017-12-18T18:38:05Z

Created page with "Category:Nixpkgs Category:Discussion Many software platforms provide their own package management tools and maintain their own public software repositories. This is..."

New page

[[Category:Nixpkgs]]
[[Category:Discussion]]

Many software platforms provide their own package management tools and maintain their own public software repositories.

This is helpful for Nixpkgs, because it means that discrete units of code are already available. They're often versioned, and sometimes already have digests attached.

This is a challenge for Nixpkgs, because Nix needs to adapt the conventions of these foreign systems to its own.