On 15-11-25 03:51pm, Franz Pletz wrote:
> Don't worry, no advertising for our company will take place. We're not
> yet using NixOS here but we're actively trying to infect all our
> co-workers and the management. Having an active local community is one
> of the best first steps in our opinion. ;)
Lots of good points, definitely experiencing most of these issues myself
(especially the SSL issues lately).
In terms of language support, it seems that we're slowly getting there.
That's what I got from NixCon, lots of people interested in helping out.
But yeah, it takes time. I think that first
> Quick question: have you tried the -P option as in `nix-env -iPf
> packages.nix` ?
No I haven't – not sure I'd want to have having multiple versions of
the same derivation name – do you maybe mean "-r"?
alexander
___
nix-dev mailing list
Alexander, I agree whole heartedly with your points.
I've experienced many of these issues too, I've also tried rolling it
out in companies but for the very reasons you mention it wasn't
adopted.
I suspect if the nix community nails each one of these issues then Nix
can go mainstream.
Alexander: I agree with most of your points. It would be really nice to
have them in github issue tracker so they can be discussed.
If you write a tutorial with code samples, I'm happy to help and make sure
it will be visible to newcomers.
Domen
On Thu, Nov 26, 2015 at 3:03 PM, stewart
Hello,
I want to do a simple thing.
When running a default.nix:
with import {};
{
projnameEnv = myEnvFun {
name = "projname";
buildInputs = [ stdenv rustcMaster cargo nanomsg];
};
}
then execute nix-shell I don't get an error and the rust project correctly
Great -- thanks Domen! I definitely intend to take you up on your
offer and I will also try to file some bugs (and maybe the odd PR). I
might not get around to that till the weekend, but it would great to
get the ball rolling soon.
alexander
On 26 November 2015 at 14:17, Domen Kožar
