Dear Nix developers,
on 2016-04-16, the Linux User Group Augsburg e.V. will host a yearly
regional Linux day -- for the 15h time. This is by far not an
international event, but we are the biggest such event in Southern
Germany, expecting 300 visitors.
We'd welcome a talk, workshop, or booth on
Hi! I've tried to start this discussion a couple times on IRC, but it
hasn't really gotten attention, so:
I'm one of the developers of Monte, a new programming language. We don't
want to write a package manager, because package managers are hard. (Also
we've been watching npm happen for the past
Quoting stewart mackenzie (2016-02-09 18:32:01)
> We're doing almost exactly this at github.com/fractalide/fractalide.
> Fractalide is a Flow-based programming language implemented in Rust
>
> We're also facing many of the issues you are :-)
>
> Rust has a slow compilation, so nix's lazy
There are so many details to distributing software. Let me quickly take a
try to dump my thoughts.
Have a static metadata file that is well defined (has a specification with
a version number of the format).
If you pick JSON, be aware it doesn't allow comments by specification. If
you add
Hi,
While I don't work on any new language I do work with large sets of packages
which I have to keep stable and at the same time develop them.
What bothers me with in most programming languages and their package managers
is that there is no known-good-set of working together packages. Stackage
I’ve used a shared nix store between VMs in the past, until the sqlite database
got corrupted…
If I’d do it again, I would configure a single build VM ( nix.buildMachines )
and set nix.maxJobs to 0. That guarantees all builds are executed on this one
machine. Any nix store copying after the
> On Feb 8, 2016, at 10:15 AM, Wout Mertens wrote:
> The problem with nfs nix stores is that the metadata is stored in sqlite,
> which can't guarantee proper locking on nfs. However, if you only write from
> one host, there is no problem.
>
> As for the python stuff,