Nixpkgs/Building RPM DEB with nixpkgs - Revision history

imported>Sikmir at 07:01, 18 October 2022

2022-10-18T07:01:29Z

← Older revision		Revision as of 07:01, 18 October 2022
Line 47:		Line 47:
	args = {		args = {
	diskImage = vm;		diskImage = vm;
			diskImageFormat = "qcow2";
	src = pkgs.ncurses.src;		src = pkgs.ncurses.src;
	name = "ncurses-deb";		name = "ncurses-deb";

imported>Matthiasbeyer: Do not mention "the author"

2019-03-29T08:22:46Z

Do not mention "the author"

← Older revision		Revision as of 08:22, 29 March 2019
Line 20:		Line 20:
	The host machine has to be prepared for the build process.		The host machine has to be prepared for the build process.

	In the ~~setting the author of~~ this article ~~used~~, ~~the host machine was~~ a CentOS 7 amd64 machine running in vmware.		In the evaluation for this article, a CentOS 7 amd64 machine running in vmware was used.
	On the machine, the nix package manager was installed via <code><nowiki>curl https://nixos.org/nix/install \| sh</nowiki></code> as suggested on https://nixos.org/nix/ > "Get Nix".		On the machine, the nix package manager was installed via <code><nowiki>curl https://nixos.org/nix/install \| sh</nowiki></code> as suggested on https://nixos.org/nix/ > "Get Nix".

Line 34:		Line 34:
	== How to build a deb/rpm with nixpkgs ==		== How to build a deb/rpm with nixpkgs ==

	The ~~author~~ used a ~~simple approach~~:		The following approach can be used to try out building a <code>.deb</code> package with nixpkgs:

	# Clone the official nixpkgs repository into <code>~/nixpkgs</code>		# Clone the official nixpkgs repository into <code>~/nixpkgs</code>

imported>Das-g: fix/wikify numbered list

2019-03-28T23:16:15Z

fix/wikify numbered list

← Older revision		Revision as of 23:16, 28 March 2019
Line 36:		Line 36:
	The author used a simple approach:		The author used a simple approach:

	1. Clone the official nixpkgs repository into <code>~/nixpkgs</code>		# Clone the official nixpkgs repository into <code>~/nixpkgs</code>
	2. Add a file to the nixpkgs repository <code>./deb.nix</code> with the following contents:		# Add a file to the nixpkgs repository <code>./deb.nix</code> with the following contents:

	(In this scenario, ncurses was built for testing the whole approach)		(In this scenario, ncurses was built for testing the whole approach)

imported>Das-g: spell out what is supposedly meant by "the curl->sh"

2019-03-28T23:14:27Z

spell out what is supposedly meant by "the curl->sh"

← Older revision		Revision as of 23:14, 28 March 2019
Line 21:		Line 21:

	In the setting the author of this article used, the host machine was a CentOS 7 amd64 machine running in vmware.		In the setting the author of this article used, the host machine was a CentOS 7 amd64 machine running in vmware.
	On the machine, the nix package manager was installed via ~~the~~ <code>curl->sh</code> ~~provided~~ on ~~the~~ nixos.org ~~website~~.		On the machine, the nix package manager was installed via <code><nowiki>curl https://nixos.org/nix/install \| sh</nowiki></code> as suggested on https://nixos.org/nix/ > "Get Nix".

	The configuration file <code>/etc/nix/nix.conf</code> was edited for the following contents:		The configuration file <code>/etc/nix/nix.conf</code> was edited for the following contents:

imported>Das-g: wikify inline code snippets. (Backticks are MarkDown syntax, not MediaWiki syntax.)

2019-03-28T23:09:08Z

wikify inline code snippets. (Backticks are MarkDown syntax, not MediaWiki syntax.)

← Older revision		Revision as of 23:09, 28 March 2019
Line 21:		Line 21:

	In the setting the author of this article used, the host machine was a CentOS 7 amd64 machine running in vmware.		In the setting the author of this article used, the host machine was a CentOS 7 amd64 machine running in vmware.
	On the machine, the nix package manager was installed via the `curl->sh` provided on the nixos.org website.		On the machine, the nix package manager was installed via the <code>curl->sh</code> provided on the nixos.org website.

	The configuration file `/etc/nix/nix.conf` was edited for the following contents:		The configuration file <code>/etc/nix/nix.conf</code> was edited for the following contents:
	<syntaxHighlight>		<syntaxHighlight>
	sandbox = false		sandbox = false
Line 36:		Line 36:
	The author used a simple approach:		The author used a simple approach:

	1. Clone the official nixpkgs repository into `~/nixpkgs`		1. Clone the official nixpkgs repository into <code>~/nixpkgs</code>
	2. Add a file to the nixpkgs repository `./deb.nix` with the following contents:		2. Add a file to the nixpkgs repository <code>./deb.nix</code> with the following contents:

	(In this scenario, ncurses was built for testing the whole approach)		(In this scenario, ncurses was built for testing the whole approach)
Line 55:		Line 55:
	</syntaxHighlight>		</syntaxHighlight>

	and then this file was called: `nix-build ./deb.nix`.		and then this file was called: <code>nix-build ./deb.nix</code>.

	This loads the relevant disk images from the channel mirror and spins up the Qemu VM to build the package.		This loads the relevant disk images from the channel mirror and spins up the Qemu VM to build the package.
	The deb file (in this case, as we're building a deb with the expression from above) is located in ./result/debs/ after a successful build.		The deb file (in this case, as we're building a deb with the expression from above) is located in ./result/debs/ after a successful build.

imported>Matthiasbeyer: Created page with initial information

2019-03-28T10:32:43Z

Created page with initial information

New page

{{expansion}}

----

Please note that this page is under construction and the provided information is incomplete. Reach out to [https://github.com/matthiasbeyer matthiasbeyer] if this page was not updated in a long time.

----

== How it works ==

To build deb/rpm packages with nix/nixpkgs, it is critical to understand the process. Hence a short intro:

To build a deb or rpm package with nixpkgs, the build process needs a ''disk image'' which it then uses to boot a virtual machine (as in Qemu). Inside this virtual machine, the deb/rpm package is compiled from a ''tarball'' and then packaged using the respective tools for deb/rpm packaging.

Luckily, all that requirements are shipped inside nixpkgs itself.

== Preparation of the host machine ==

The host machine has to be prepared for the build process.

In the setting the author of this article used, the host machine was a CentOS 7 amd64 machine running in vmware.
On the machine, the nix package manager was installed via the `curl->sh` provided on the nixos.org website.

The configuration file `/etc/nix/nix.conf` was edited for the following contents:
<syntaxHighlight>
sandbox = false
system-features = [ kvm nixos-test benchmark big-parallel ]
</syntaxHighlight>

This step might not be necessary on a NixOS installation.

== How to build a deb/rpm with nixpkgs ==

The author used a simple approach:

1. Clone the official nixpkgs repository into `~/nixpkgs`
2. Add a file to the nixpkgs repository `./deb.nix` with the following contents:

(In this scenario, ncurses was built for testing the whole approach)

<syntaxHighlight lang=nix>
let
pkgs = (import ./default.nix {});
vm = pkgs.vmTools.diskImageFuns.centos7x86_64 {};
args = {
diskImage = vm;
src = pkgs.ncurses.src;
name = "ncurses-deb";
buildInputs = [];
meta.description = "No descr";
};
in pkgs.releaseTools.debBuild args
</syntaxHighlight>

and then this file was called: `nix-build ./deb.nix`.

This loads the relevant disk images from the channel mirror and spins up the Qemu VM to build the package.
The deb file (in this case, as we're building a deb with the expression from above) is located in ./result/debs/ after a successful build.