It's not really that straightforward, because `nix-env` is a part of Nix,
but `configuration.nix` is a configuration of NixOS. Those are two
different projects.
Furthermore, it is not really correct to say that “`nix-env` reads” or
“does not read” `configuration.nix`. It reads the expression it
Hi Cody,
haskellngPackages doesn't seem to have all versions of all dependencies...
I'm not sure what you mean by all versions of all dependencies. Dependencies
of what exactly? The way I understand the term, dependency has meaning only
as a relationship between two packages, i.e. transformers
I'm very new to NixOS; perhaps this isn't the correct venue to ask this
sort of question, in which case I would appreciate guidance about where
better to ask.
In trying to use the couchdb package, I found a couple of issues with
its pre-start script[1]. My PR
Talking about laws: are there any guidelines about what software can go into
nixpkgs/can be distributed by hydra?
I know many distributions try to somehow separate the software illegal in USA
(mostly DRM-related/patented stuff).
Kirill Elagin kirela...@gmail.com napisał:
As far as I understand,
On 02/15/2015 09:54 AM, James Cook wrote:
Hard linking is an impurity which can
cause bugs, as Wout pointed out at the start of the thread (e.g.
https://github.com/NixOS/nixpkgs/issues/4266).
Implementation question: how would nix know when it can delete a file
in /nix/store/.links?
If you
On 02/22/2015 11:26 AM, Tomasz Kontusz wrote:
Talking about laws: are there any guidelines about what software can go
into nixpkgs/can be distributed by hydra?
I know many distributions try to somehow separate the software illegal
in USA (mostly DRM-related/patented stuff).
Basically anything
On 22 February 2015 at 18:05, Rok Garbas r...@garbas.si wrote:
However, we could rename dead branches to something like attic/name.
Yes, that's sounds better than what we have now. Alternatively, we
could make a historic repo clone (like Nathan Bijnens suggests).
nixpkgs-historic? Then we
I've cleaned up some merged branches.
On Sun, Feb 22, 2015 at 9:05 AM, Rok Garbas r...@garbas.si wrote:
However, we could rename dead branches to something like attic/name.
Yes, that's sounds better than what we have now. Alternatively, we
could make a historic repo clone (like Nathan
I just do `nix-shell --add-root result` as I have result in global
.gitignore.
Could be done easier probably :)
On Sun, Feb 22, 2015 at 7:25 AM, Michael Ekstrand mich...@elehack.net
wrote:
In the source directory for one of my local projects, I have created a
'default.nix' file that pulls in
On the long run NixOps needs a cleaner API to handle the state.
The result could be centralized deployments (via web api) or just a
plaintext file stored in git.
PS: Making sure you're aware of https://github.com/zalora/upcast
On Sat, Feb 21, 2015 at 4:06 PM, Thomas Hunger tehun...@gmail.com
On Sat, Feb 21, 2015 at 4:06 PM, Thomas Hunger tehun...@gmail.com wrote:
We also have a CI server which deploys for us, but that's not the same
server as the common one we use for manual deploys (which are unfortunately
necessary on occasion). So we have two copies of the state which has
On 17 February 2015 at 10:44, Eelco Dolstra eelco.dols...@logicblox.com wrote:
Hi,
On 16/02/15 18:43, Matthias Beyer wrote:
what do you think about removing the old branches, as listed below (I
guess all before 12-2014 or something) should be removed,...
No, they should not be removed,
On 02/22/2015 07:59 AM, Chad Joan wrote:
Is there a way for me to discover other useful configuration options
like this?
AFAIK the only complete way is just to read the source expressions of
what you're interested in, e.g. in this case:
However, we could rename dead branches to something like attic/name.
Yes, that's sounds better than what we have now. Alternatively, we
could make a historic repo clone (like Nathan Bijnens suggests).
nixpkgs-historic? Then we have an option to clean up some less used
branches/tags in the
22. feb. 2015 08:29 skrev Cody Goodman codygman.consult...@gmail.com
følgende:
[...]
For some reason nix can't seem to find it...
~ $ grep -A3 helloEnv /etc/nixos/configuration.nix
53: helloEnv = pkgs.myEnvFun {
54-name = someEnvName;
55-buildInputs = [ hello ];
Could you expand on this a bit? I've been using nixops for a while, but
only recently set up a Hydra server to run tests automatically. I'm now
considering doing automated deployments out of hydra, but not quite sure
how that should work. It would be simple to have a hydra job that runs
Hi Cody,
I'll look into it asap, thanks.
On Sun, Feb 22, 2015 at 09:20:44PM -0600, Cody Goodman wrote:
[cody@cody-nixos:~]$ nix-env -iA nixos.pkgs.idea.android-studio
replacing old a**android-studio-1.1.0b2a**
installing a**android-studio-1.1.0b2a**
building path(s)
I see. Thank you for being up-front about it.
That link is helpful; I've been reading a thing or two in all-packages.nix
as needed, but I didn't realize these options would be defined there.
This really reminds me of Gentoo USE flags. I can't blame anyone for not
wanting to go around
Saved ~23GB when I first ran nix-store --optimise (a week ago). Although I
hadn't garbage collected for some time.
Did a garbage collection today (the first for quite some time):
note: currently hard linking saves 25906.96 MiB
67613 store paths deleted, 48738.67 MiB freed
My /nix/store is on a
[cody@cody-nixos:~]$ nix-env -iA nixos.pkgs.idea.android-studio
replacing old ‘android-studio-1.1.0b2’
installing ‘android-studio-1.1.0b2’
building path(s)
‘/nix/store/2dbhhwl1qswy2b7ii0cybi1vrfqq1h23-user-environment’
created 1266 symlinks in user environment
[cody@cody-nixos:~]$ nix-env -iA
20 matches
Mail list logo
