Oh I see, that clear things up a bit.
On Wed, May 3, 2017, at 11:50 PM, Marc Weber wrote:
> configuration.nix option nixpkgs.config is what ~/.nixpkgs/config.nix is
> for the user in case you missed it.
>
> Thus:
>
> nixpkgs.config.allowUnfree = true;
> nixpkgs.config.packageOverrides = p:
configuration.nix option nixpkgs.config is what ~/.nixpkgs/config.nix is for
the user in case you missed it.
Thus:
nixpkgs.config.allowUnfree = true;
nixpkgs.config.packageOverrides = p: ..
You don't have to use config.nix if this is all you need.
Marc Weber
1) misc.* is best looked by using ctagsWrapped on nixpkgs then looking
for misc. (or use grep)
You'll find pkgs/misc/misc.nix:
collection = {list, name} : runCommand "collection-${name}" {} ''
mkdir -p $out/nix-support
echo ${builtins.toString list} >
Using that repo, I have been able to reach what I was looking for: my
system config uses configuration.nix, just for the system, and internet
facing stuff, where I really want to follow the release channel to make
sure I use the latest.
For my user stuff, I now have a config.nix:
$ cat
On Wed, May 3, 2017, at 10:33 PM, Kamil Chmielewski wrote:
> Hi John,
> you could find my https://github.com/kamilchm/.nixpkgs helpfull.
> I use config.nix to manage user pacakges and dofiles and link them
> into ~ with simple script
> https://github.com/kamilchm/.nixpkgs/blob/master/install.sh>
$ cat ~/.config/nixpkgs/config.nix
with import {};
{
allowUnfree = true;
graphicCollection = misc.collection {
name = "foo" ;
packages = [
vlc
];
};
}
$ nix-env -i misc.collection.graphicCollection
error: selector
Or ask google "nix/os/nixpkgs config.nix" to find samples and get
inspiration from
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev
Hi John,
you could find my https://github.com/kamilchm/.nixpkgs helpfull.
I use config.nix to manage user pacakges and dofiles and link them into ~
with simple script
https://github.com/kamilchm/.nixpkgs/blob/master/install.sh
Best regards,
Kamil
2017-05-04 3:55 GMT+02:00 John Ramsden
> I don't like the idea of using nix-env,
Why? You can also have your own declarative set of packages "per user".
that's also something config.nix can do:
graphicCollection = misc.collection { name = ... ; packages = [ ... . ]} (from
head)
nix-env -i graphicCollection
works well for me :)
Thanks, for the information.
Marc Weber mentioned
1) you can install system wide (nixos-rebuild ..)
2) you can install as user into ~/.nix-profile.nix
~/.config.nix is to "customize" user nixpkgs by
- setting settings such as allowUnfree
- override mplayer to use library X
- add
Here's some links for reference:
* https://github.com/NixOS/nixpkgs/issues/1750
* https://github.com/sheenobu/nix-home
*
http://sandervanderburg.blogspot.com.au/2013/09/managing-user-environments-with-nix.html
*
> $HOME/.nixpkgs/config.nix file works.
1) you can install system wide (nixos-rebuild ..)
2) you can install as user into ~/.nix-profile.nix
~/.config.nix is to "customize" user nixpkgs by
- setting settings such as allowUnfree
- override mplayer to use library X
- add your own packages
Hi John,
I guess the reason you are not receiving many answers is that your
question highlights some misconceptions, and some design issues with nix.
There does not exist any declarative configuration file for user
environments. /etc/nixos/configuration.nix is amazing, but has not been
I've been looking for some information about how exactly the
$HOME/.nixpkgs/config.nix file works. How exactly is it intended to be
used? Up until now I've been managing my entire system from /etc/nixos,
but it would be nice to have a place where I can add something that
happens only to a
14 matches
Mail list logo