Channel branches: Difference between revisions

← Older edit Newer edit →

VisualWikitext

Revision as of 10:18, 24 December 2023 view source imported>Hannses m changed 23.05 to 23.11 (forgot one) ← Older edit		Revision as of 16:27, 1 April 2024 view source Fricklerhandwerk (talk \| contribs) 25 edits wording and formatting Tag: Visual edit Newer edit →
Line 1:		Line 1:
	Nixpkgs is the ~~git~~ repository containing all ~~packages~~ and NixOS ~~modules/expressions~~. Installing packages directly from the master branch of the Nixpkgs ~~repo~~ is possible, but risky, since ~~git~~ commits are merged into master before being heavily tested. That's where ~~channels~~ are useful.		Nixpkgs is the Git repository containing all package reciptes and NixOS module declarations. Installing packages directly from the <code>master</code> branch of the Nixpkgs repository is possible but risky, since Git commits are merged into <code>master</code> before being heavily tested. That's where channel branches are useful.

	A "channel" is a name for the latest "verified" git commits in Nixpkgs. Each channel has a different definition of what "verified" means. Each time a new git commit is verified, the channel declaring this verification gets updated. Contrary to a user of the git master branch, a channel user will benefit from both verified commits and binary packages from the binary cache.		A "channel" is a name for the latest "verified" git commits in Nixpkgs. Each channel has a different definition of what "verified" means. Each time a new git commit is verified, the channel declaring this verification gets updated. Contrary to a user of the git master branch, a channel user will benefit from both verified commits and binary packages from the binary cache.