environment; that is, an operating system environment in which there
is (essentially) only a store.
The script `make-disk.sh' creates an ext2 disk image, creates a Nix
store in it, and copies the closure of the bash package (from
nixpkgs) to it. The script `run.sh' then starts bash in a UML
virtual machine.
The contents of the image after creation look like this:
$ ls -l
drwxr-xr-x 2 root root 1024 2004-02-14 19:13 dev
lrwxrwxrwx 1 root root 61 2004-02-14 23:34 init -> /nix/store/e40873ece7a010752ad72b4262b23d28-bash-2.05b/bin/sh
drwx------ 2 root root 12288 2004-02-14 19:13 lost+found
drwxr-xr-x 4 root root 1024 2004-02-14 19:13 nix
drwxr-xr-x 2 root root 1024 2004-02-14 19:13 proc
drwxrwxrwt 2 root root 1024 2004-02-14 19:13 tmp
The next step is to add all the other stuff that goes into a working
system (coreutils, etc.). BTW, if you don't have `ls' you can still
list directories by doing `echo *' :-)
Nix itself should also be Nixified so that it can be put into the
store.
svn path=/nixu/trunk/; revision=783
stages of the bootstrap process (i.e., stdenvLinuxBoot).
* Add those packages to the distribution. We didn't do that before
because it would cause them to be built twice.
svn path=/nixpkgs/trunk/; revision=753
a big problem, so I decided to require to user to get the
file and put it in some location in the file system. wget
doesn't seem to accept the file scheme however, so I had to
move the copying into the builder itself. The builder checks
the md5 hash of the downloaded file. Maybe having a separate
'fetchfile' would be useful to make a file in the outside
world pure. I tried to add this to build-support, but this
obviously did not work. I still committed it. Just remove it
if you think that it sucks.
svn path=/nixpkgs/trunk/; revision=716
is to fully automate the building of distributions and
their release for distribution through a web-site, ftp
directory, etc. Inspired by nix-dist, but more generic
in order to deal with StrategoXT and related packages.
The assumptions are the following:
- package source is a subversion repository
- the package is under autotool configuration
(at least it has a configure.in with an AC_INIT)
- standard autotools build interface:
- bootstrap; configure; make install;
make check; make dist
- optionally the release status can be indicated by
a status="..." definition in configure.in
Creation of distributions is a two-step process:
urls-to-nix.sh # nix expressions for most recent commits
build+upload.sh # instantiate the expressions
svn-to-nix.sh
Generates nix expression for head revision of the
package; revision number, package name, and version
are obtained from the source and do not have to
be declared.
urls-to-nix.sh
Contains a list of URLs to which svn-to-nix.sh is applied.
build+upload.sh
Builds the packages and creates distributions in a www
directory. Including the log of the build process (buildfarm)
and files such as NEWS and README (for release management).
(upload part of the script is currently turned off)
do-it.nix
Top nix expression; collects pointers to required packages
(e.g., stdenv, autotools, aterms, ...) and binds them
to the parameters of the source-dist.nix packages.
package-source-dist.nix
Generic Nix expression for a package parameterized with
version info from svn and dependency info from do-it.nix.
package-dist.nix
Generated; just imports
package-version-rev.nix
Generated; instantiates package-source-dist.nix with version,
name, packagename, rev.
build-from-svn.sh
Generic build script; obtains configuration flags from
with... and enable... attributes of the Nix expression.
Creates logs of the various parts of the build process.
Creates distribution
Generalizations:
- Currently some information about a package resides in
this directory, e.g., the generic Nix expression for
a package, and the composition of the overall do-it.nix
This information should also be obtained from the source
tree.
- Upload facility lacking.
svn path=/nixpkgs/trunk/; revision=605
