> RST is best.
I don't get this attitude. Documentation has to be easy to write, or
very few people will do it. At least 90% of developers know and prefer
Markdown over everything else, even if the syntax has fundamental flaws.
On Sat, Apr 16, 2016, at 01:44 AM, Anderson Torres wrote:
>
GNOME 3 works pretty well, but like many other things on NixOS it has a
few quirks. For example, it does not auto-detect new apps until you
restart GNOME shell. I wouldn't recommend NixOS to non-developers, our
stable releases are still a lot less stable than Debian testing.
On Sat, Apr 9, 2016,
I'd estimate around 10 years of development until all of the blockers
are implemented, so we might as well drop AMD64 and release for the
ARM128 architecture only.
On Fri, Apr 1, 2016, at 12:21 PM, Lluís Batlle i Rossell wrote:
> Sorry, I think that we also mentioned in the meeting that we would
FYI npm also uses @ for this purpose (e.g. npm install foo@1.0). I don't
think I ever had to escape it (?).
On Wed, Mar 30, 2016, at 10:32 AM, Vladimír Čunát wrote:
> On 03/29/2016 02:33 PM, Arseniy Seroka wrote:
> > I saw post about guix release and there was introduced a '@'
> > delimiter in
Very cool project, thanks for the link!
On Wed, Mar 23, 2016, at 05:38 AM, Colin Putney wrote:
> Looks interesting, and credits nix as an inspiration:
>
> https://github.com/alexanderGugel/ied
>
>
>
> -Colin
> _
> nix-dev mailing list
>
> So I wouldn't generally do that on an Internet-facing system -
> security patches are not always applied to the latest stable release,
> never mind the one before that.
Please, if you see that happening, open an issue (or, even better,
submit a PR). This is definitely an area we need to
> So I wouldn't generally do that on an Internet-facing system -
> security patches are not always applied to the latest stable release,
> never mind the one before that.
Please, if you see that happening, open an issue (or, even better,
submit a PR). This is definitely an area we need to
The obvious other solution is to use 16.03, I don't think there is much
else you can do.
On Sat, Mar 19, 2016, at 08:33 AM, Moritz Angermann wrote:
> Hi,
>
> I want to build a nixos based on 15.09, but use gitlab
> from master. Thus I basically want to use the 15.09
> channel and layer gitlab[1]
What is packaged is just the compiler and related tools, not the
packages from package.elm-lang.org.
On Tue, Feb 23, 2016, at 10:19 AM, Rok Garbas wrote:
> it looks there is some support for elm packages. not sure about the
> documentation but you can ping people which touched those files [1].
>
Interesting, that looks like a good way to reduce the amount of open
issues. I've signed up.
On Tue, Feb 16, 2016, at 11:43 PM, Profpatsch wrote:
> I just created a Repo page for nixpkgs at codetriage.com.
>
> It is a simple site that sends you 1 open issue each day once
> you sign up with your
What prevents you from doing it? You only need a way to figure out which
machine you are on, I did that by adding configuration.nix to my
gitignore and then loading the machine configuration from there.
https://github.com/jgillich/nixos
https://nixos.org/wiki/Real_World_NixOS_Dotfiles
On Thu,
I agree that the current folder structure is a mess. There is a severe
lack of structure, often there are further category-folders in a folder
with packages (like misc/, misc/themes/).
FreeBSD has categories at the root level, everything below are packages:
Somehow Fastmail didn't actually replace the link, but only the link text :(. I
wanted to link to:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html[1]
On Fri, Jan 8, 2016, at 03:48 AM, Jakob Gillich wrote:
> I agree that the current folder struct
Oh I never said we should take the same categories, just that
/ is a sane structure. devel for example could be devel-
python, devel-ruby etc, just like the current langPackages.
On Fri, Jan 8, 2016, at 04:35 AM, Mathnerd314 wrote:
> On Thu, Jan 7, 2016 at 7:48 PM, Jakob Gillich
&g
> I think there are few enough people who contribute to the nix repo as it is
> now.
That is actually an argument in favor of a rewrite, C++ is not very
popular in the Linux community. Contributing to Nix will become a lot
more attractive when it's written in a language that people actually
Nix doesn't have to be rewritten at once; you can rewrite the Perl stuff
in Rust and call them from C++ code via a C interface[1]. This is what
Mozilla does in Firefox, which is also mostly C++. So the question
should be, do we want to get rid of C++ in the long term?
[1]:
Hi,
there is a open PR for the same thing with wpa_supplicant:
https://github.com/NixOS/nixpkgs/pull/12015
But declarative configuration of Networkmanger would be nice to
have, too!
On Wed, Dec 30, 2015, at 04:54 PM, Mateusz Czaplinski wrote:
> Hi All. I've recently installed NixOS on an old
Impressive, thanks for this! Also wondering if it would work on OpenVZ?
Oh and a switch to simply wipe the old system could be useful. One can
always redeploy the old OS if something goes wrong.
On Wed, Dec 9, 2015, at 08:59 PM, jeaye wrote:
> Folks,
>
> In hopes of getting NixOS onto
I'm also pretty new to Nix and in my experience, the manual is pretty good and
covers a lot of topics, but it doesn't rank very well on Google. For example,
when I search for "nixos containers" on Google, I get:
1. The manual entry from 14.12
2. The wiki page NixOS:Containers, which is rather
19 matches
Mail list logo
