max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-22 22:16:16 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
nix-super/scripts/Makefile.am

29 lines
1,014 B
Text
Raw Normal View History

* Maintain integrity of the substitute and successor mappings when deleting a path in the store. * Allow absolute paths in Nix expressions. * Get nix-prefetch-url to work again. * Various other fixes.
2003-11-22 20:45:56 +02:00
bin_SCRIPTS = nix-collect-garbage \
* A utility script `nix-build' that builds Nix expressions and prints their output paths (and only that) on standard output.
2004-06-22 18:12:34 +03:00
nix-pull nix-push nix-prefetch-url \
* New tools nix-pack-closure and nix-unpack-closure. These provide a useful way to transfer the closure of a store path to another machine. These commands provide functionality previously possible through `nix-push --copy'. However, they are much more convenient in many situations (though possibly less efficient). Example: $ nix-pack-closure /nix/store/hj232g1r...-subversion-1.3.0 > svn.closure (on another machine:) $ nix-unpack-closure < svn.closure Note that Subversion is added to the store, but not installed into a user environment. One should do `nix-env -i /nix/store/hj232g1r...-subversion-1.3.0' for that. Another example: copy the application Azureus to the machine `scratchy' through ssh: $ nix-pack-closure $(which azureus) | ssh scratchy nix-unpack-closure
2006-01-12 17:17:51 +02:00
nix-install-package nix-channel nix-build \
nix-pack-closure nix-unpack-closure
* We no longer use nix-populate standalone, rather we use it as a build action for `system' packages (like system.fix) that have dependencies on all packages we want to activate. So the command sequence to switch to a new activation configuration of the system would be: $ fix -i .../fixdescriptors/system.fix ... system.fix -> 89cf4713b37cc66989304abeb9ea189f $ nix-switch 89cf4713b37cc66989304abeb9ea189f * A nix-profile.sh script that can be included in .bashrc.
2003-04-09 15:26:48 +03:00
* Added a disambiguation heuristic: if two components have the same name but differ to much in sice (by more than a factor of 3), then never generate a patch.
2005-02-28 16:12:06 +02:00
noinst_SCRIPTS = nix-profile.sh generate-patches.pl
* Generate the scripts so that we can substitute the prefix etc. correctly. * Fixed nix-switch.
2003-07-13 21:58:03 +03:00
* Place manifests in /nix/var/nix/manifests. * Use the new patch downloader.
2004-12-20 18:38:50 +02:00
nix-pull nix-push: readmanifest.pm download-using-manifests.pl
* Refactoring: put the manifest-reading code in a separate file.
2003-12-05 13:25:38 +02:00
* Place manifests in /nix/var/nix/manifests. * Use the new patch downloader.
2004-12-20 18:38:50 +02:00
install-exec-local: readmanifest.pm download-using-manifests.pl
* RPM spec file. * Respect DESTDIR variable.
2003-12-30 22:09:00 +02:00
$(INSTALL) -d $(DESTDIR)$(sysconfdir)/profile.d
$(INSTALL_PROGRAM) nix-profile.sh $(DESTDIR)$(sysconfdir)/profile.d/nix.sh
$(INSTALL) -d $(DESTDIR)$(libexecdir)/nix
$(INSTALL_DATA) readmanifest.pm $(DESTDIR)$(libexecdir)/nix
* Place manifests in /nix/var/nix/manifests. * Use the new patch downloader.
2004-12-20 18:38:50 +02:00
$(INSTALL_PROGRAM) download-using-manifests.pl $(DESTDIR)$(libexecdir)/nix
* RPM spec file. * Respect DESTDIR variable.
2003-12-30 22:09:00 +02:00
$(INSTALL) -d $(DESTDIR)$(sysconfdir)/nix
* Generate the scripts so that we can substitute the prefix etc. correctly. * Fixed nix-switch.
2003-07-13 21:58:03 +03:00
* Generate nar.sh, fetchurl.sh.
2003-07-18 10:42:57 +03:00
include ../substitute.mk
* Incorporated Berkeley DB and ATerm into the source tree. * `make dist'.
2003-07-23 18:53:34 +03:00
* One-click installation :-) The script nix-install-package takes a `Nix package file' (which contains one or more derivations, along with URLs of Nix caches), unpacks it, pulls the caches, and installs the derivations in the user's environment. For best results, associate the command `xterm -e /nix/bin/nix-install-package' with the MIME type `application/x-nix-package' and visit http://losser.st-lab.cs.uu.nl/~eelco/test/.
2003-11-24 13:11:40 +02:00
EXTRA_DIST = nix-collect-garbage.in \
* A utility script `nix-build' that builds Nix expressions and prints their output paths (and only that) on standard output.
2004-06-22 18:12:34 +03:00
nix-pull.in nix-push.in nix-profile.sh.in \
nix-prefetch-url.in nix-install-package.in \
nix-channel.in \
* Remove `prebuilts.conf' file, it's not like anybody was using it. * Add /nix/var/nix/manifests directory.
2004-12-16 16:31:49 +02:00
readmanifest.pm.in \
* Place manifests in /nix/var/nix/manifests. * Use the new patch downloader.
2004-12-20 18:38:50 +02:00
nix-build.in \
* Add missing file to dist.
2005-03-01 13:27:22 +02:00
download-using-manifests.pl.in \
* New tools nix-pack-closure and nix-unpack-closure. These provide a useful way to transfer the closure of a store path to another machine. These commands provide functionality previously possible through `nix-push --copy'. However, they are much more convenient in many situations (though possibly less efficient). Example: $ nix-pack-closure /nix/store/hj232g1r...-subversion-1.3.0 > svn.closure (on another machine:) $ nix-unpack-closure < svn.closure Note that Subversion is added to the store, but not installed into a user environment. One should do `nix-env -i /nix/store/hj232g1r...-subversion-1.3.0' for that. Another example: copy the application Azureus to the machine `scratchy' through ssh: $ nix-pack-closure $(which azureus) | ssh scratchy nix-unpack-closure
2006-01-12 17:17:51 +02:00
generate-patches.pl.in \
nix-pack-closure.in nix-unpack-closure.in
Reference in a new issue Copy permalink