Re: [Nix-dev] User-oriented nixpkgs documentation (was: ioquake3 on nixos)

[Jakob Gillich]

> 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:
> 2016-04-15 13:54 GMT-03:00 Profpatsch :
> > On 16-04-09 04:10pm, Anderson Torres wrote:
> >> I prefer to start a documentation project, like the FreeBSD
> >> Handbook[1]. It could contain some in-project documentation for every
> >> module too.
> >
> > I proposed a Cookbook a while ago, akin to the Puppet one
> > http://www.puppetcookbook.com/
> >
> > We could write that in Asciidoc or Markdown (or rst).
> 
> RST is best.
> 
> >
> > --
> > Proudly written in Mutt with Vim on NixOS.
> > Q: Why is this email five sentences or less?
> > A: http://five.sentenc.es
> > May take up to five days to read your message. If it’s urgent, call me.
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] few questions before migrating from Debian…

[Jakob Gillich]

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, at 09:07 PM, Saša Janiška wrote:
> Hello,
> 
> for some time I’m considering which Linux distro to use to have
> relatively fresh packages as well as not to waste too much time for
> admin work.
> 
> Morever, it would be ideal to have same distro for the machine of my
> relative’s to make it easier during trouble.shooting session. So, in
> order to fulfill those two requirements I did consider to stay with
> Debian (Sid) on my desktop and netbook machines, but put Debian Stable
> on the machines of my relatives.
> 
> However, after checking about NixOS which I tried many years ago, I’ve
> concluded it’s the best option at the moment since I learnt that
> nixos-stable might be good-enough for other’s machine requiring not much
> admin time, while I can use nixos-unstable if stable channel is not
> fresh–enough for my own needs.
> 
> So, before jumping to install on real hardware - today I did install
> under vbox, I’ve few questions…
> 
> My desktop is i7 2.8G/16G machine having 1xTB+1x2TB disks which are
> assembled in btrfs raid1 with / and /home as btrfs subvolumes (the
> remaining 1TB is used for daily backups.)
> 
> I’m delighted that NixOS provides ZFS as filesytem option since it was
> one of the reasons why I was evaluating Free/PC-BSD option in the past.
> 
> a) do you, in general, recommend using ZFS over Btrfs for NixOS desktop
> machine?
> 
> b) is ZFS good option even for single-disk netbook machine with 4G of
> memory?
> 
> c) can one use ZFS on root *without* usage of separate /boot partition?
> I use same disk layout on Debian, but with btrfs and do not have any
> experience with ZoL, although I’ve found that there is
> ’boot.loader.grub.zfsSupport’ option?
> 
> Any doc/tutorial explaining how to do such install?
> 
> I’ve found: https://gist.github.com/vizanto/7374277 but wonder if it is
> still relevant?
> 
> There are of course few packages I do miss in NixOS, but everything else
> is so great, so that I’m very enthusiastic to put NixOS on all my
> relative’s  machines very soon.
> 
> On all machines, I plan to use GNOME3, so wonder if there are some
> gotchas in regard - someone on #nixoes mentioned that GTK does not like
> custom paths as used by Nix and recommended i3 instead which is, atm,
> not option considering that other family members also use my machine and
> relatives are not savvy-enough for that tiling wm.
> 
> 
> Sincerely,
> Gour
> 
> -- 
> Therefore, without being attached to the fruits of activities,
> one should act as a matter of duty, for by working without
> attachment one attains the Supreme.
> 
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 16.03 release has been post-postponed (was: When will nixos-16.03 be ready?)

[Jakob Gillich]

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 also
> have a working x32 ABI NixOS release. I'm afraid that your list is not
> exhaustive.
> 
> On Fri, Apr 01, 2016 at 12:10:10PM +0200, Peter Simons wrote:
> > Christian Kauhaus writes:
> > 
> >  > I wonder what the timeline is for the 16.03 release. As far as I
> >  > understand it, it was supposed to happen in March, but odds are not
> >  > so good right now. Has anyone an idea about what it takes for the
> >  > release to happen?
> > 
> > I have the unpleasant duty of informing everyone that all plans to release
> > nixos-16.03 are OFF.
> > 
> > We were literally minutes away from tagging the source code and switching on
> > the nixos-16.03 channel when Domen realized that we had flat-out forgotten
> > to implement several important BLOCKERS that prevent us from releasing the
> > new version right now. So we had an on-line meeting, discussed our options,
> > and concluded to POSTPONE any new NixOS releases until the following issues
> > are resolved:
> > 
> >  - Re-designed UI for Nix command-line tools
> >  - Deterministic Reproducible Builds (#2281)
> >  - Security Hardening (#7220)
> >  - Fast Delivery of Security Updates (#10851)
> >  - Recursive Nix
> >  - Declarative User Environments a.k.a. User-space NixOS (#9250)
> >  - Hydra NG (#12203)
> >  - Lazier mkDerivation function (#11094)
> >  - Consistent Support for Multiple Outputs (#7701)
> > 
> > Once ALL these issues are implemented and tested, we'll start over with a
> > new release cycle.
> > 
> > Thank you for your patience and understanding,
> > Peter
> > 
> > ___
> > nix-dev mailing list
> > nix-dev@lists.science.uu.nl
> > http://lists.science.uu.nl/mailman/listinfo/nix-dev
> 
> -- 
> (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP)
> PGP key D4831A8A - https://emailselfdefense.fsf.org/
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nixpkgs versioning

[Jakob Gillich]

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 pkg's name to separate version from name. Maybe we can use it 
> > in nix too?
> 
> It seems rather unconventional and currently I can't see enough
> advantages to convince me personally.
> 
> In shell commands you will typically need to escape the character, which
> would affect commands like `nix-env -i foo\@ver` but that shouldn't
> happen too often. What would be worse, if this delimiter was used in
> filesystem paths like /nix/store/hash-fooname@version/... we would have
> to escape all of the occurrences and I'd expect many scripts to break.
> 
> --Vladimir
> 
> 
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
> Email had 1 attachment:
> + smime.p7s
>   5k (application/pkcs7-signature)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] IED, an alternate package manager for node

[Jakob Gillich]

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
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] mix and match

[Jakob Gillich]

> 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 improve, but usually
fixes are applied to master and stable at the same time. They even
arrive earlier in stable because unstable is often lagging behind.

On Sat, Mar 19, 2016, at 10:51 AM, Cameron Turner wrote:
> On 19 March 2016 at 07:33, 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] at 1cd99b1 and the gitlab
> > service[2] at 38579a1 at on top of it.
> 
> 
> 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.
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] mix and match

[Jakob Gillich]

> 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 improve, but usually
fixes are applied to master and stable at the same time. They even
arrive earlier in stable because unstable is often lagging behind.

On Sat, Mar 19, 2016, at 10:51 AM, Cameron Turner wrote:
> On 19 March 2016 at 07:33, 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] at 1cd99b1 and the gitlab
> > service[2] at 38579a1 at on top of it.
> 
> 
> 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.
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] mix and match

[Jakob Gillich]

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] at 1cd99b1 and the gitlab
> service[2] at 38579a1 at on top of it.
> 
> I’ve asked this today on IRC already.  And the proposed
> solution is to use my own nixpkgs-channels clone and
> apply patches as need, thanks joachifm!
> 
> Yet this seems like it’s easily going to end up in a
> mess and I though I’d ask here again. Is there any
> other recommended way?
> 
> Cheers,
> Moritz
> 
> [1]:
> https://github.com/NixOS/nixpkgs/tree/master/pkgs/applications/version-management/gitlab
> [2]:
> https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/gitlab.nix
> 
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Building Elm with Nix?

[Jakob Gillich]

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].
> 
> try to convince them to document it or if you do it yourself even better
> [2].
> 
> [1]
> https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/elm/default.nix
> [2] https://nixos.org/wiki/Contributing_to_Nix_documentation
> 
> 
> On Tue, Feb 23, 2016 at 5:56 AM, Anand Patil
>  wrote:
> > Hi everyone,
> >
> > Does anyone have a system worked out for building Elm projects and managing
> > their dependencies with Nix? It looks like an elmWithPackages was developed
> > in 2013, http://comments.gmane.org/gmane.comp.lang.elm.general/648, but it
> > doesn't seem to have been merged.
> >
> > Cheers,
> > Anand
> >
> > ___
> > nix-dev mailing list
> > nix-dev@lists.science.uu.nl
> > http://lists.science.uu.nl/mailman/listinfo/nix-dev
> >
> 
> 
> 
> -- 
> Rok Garbas
> http://www.garbas.si
> r...@garbas.si
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] codetriage.com

[Jakob Gillich]

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 Github account.
> 
> Maybe a few people want to join me.
> 
> -- 
> Proudly written in Mutt with Vim on NixOS.
> Q: Why is this email five sentences or less?
> A: http://five.sentenc.es
> May take up to five days to read your message. If it’s urgent, call me.
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Put configuration.nix under version control

[Jakob Gillich]

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, Jan 21, 2016, at 12:24 AM, Owen Lynch wrote:
> Hello,
>
> I'm wondering if there is a standard/recommended way to put
> /etc/nixos/configuration.nix under version control. It would make
> managing lots of virtual machines a lot easier, because I could have a
> script that updated to the latest configuration.nix and then ran nixos-
> rebuild whenever I made a change. It would also make updates even
> *more* atomic!
>
> -Owen
> _
> nix-dev mailing list nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Flattening pkgs tree in nixpkgs/pkgs

[Jakob Gillich]

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:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html[1]


Maybe this model could work for us, too?


They also have virtual categories for things like gnome; if we implement
something similar, that would allow maintainers of larger package sets
(@lethalman) to work as usual.

On Fri, Jan 8, 2016, at 01:04 AM, Tomasz Czyż wrote:
> After playing for a while with a nixpkgs repo I have impression that
> categories/directories are just waste of time.
>
> * Have to be maintained
> * Harder to find things
> * Lack of any package manager which tells about it
>
> Each time I want to find a package name I do
> * find -name '*name*' or use github search to locate files in repo.
>
> From maintaining perspective:
>
> (for x in `ls`; do n=$(ls $x|wc -l);echo "$n - $x";done)|sort -n
> 1 - backup 2 - inferno 2 - search 3 - gis 4 - display-managers 10
> - altcoins 11 - science 11 - taxes 20 - virtualization 25 - kde-apps-
> 15.12 27 - office 41 - version-management 41 - window-managers 42
> - networking 59 - video 60 - editors 85 - graphics 186 - audio
> 224 - misc
>
> Do you see that? It's hard to define all those categories levels, some
> of directories have subdirectories (like applications) other not
> (servers). It's hard to follow. Most people know the name of the
> software, if not, they probably use google to find it, not using
> categories.
>
> Let's make the layout more clear, more accessible and easy to follow.
>
> What do you think about moving all packages into flat namespace?
>
> Let's say you have
>
> pkgs/package1/default.nix pkgs/package2/default.nix
>
> or even better:
>
> pkgs/my-package.nix pkgs/gcc.nix pkgs/gcc-5.0.nix
>
> then, you can autogenerate top-level.pkgs
>
> I'm happy to help implementing that.
> _
> nix-dev mailing list nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



Links:

  1. https://freshports.org/categories.php
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Flattening pkgs tree in nixpkgs/pkgs

[Jakob Gillich]

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 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:
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html[2]
>
> Maybe this model could work for us, too?
>
> They also have virtual categories for things like gnome; if we
> implement something similar, that would allow maintainers of larger
> package sets (@lethalman) to work as usual.
>
> On Fri, Jan 8, 2016, at 01:04 AM, Tomasz Czyż wrote:
>> After playing for a while with a nixpkgs repo I have impression that
>> categories/directories are just waste of time.
>>
>> * Have to be maintained
>> * Harder to find things
>> * Lack of any package manager which tells about it
>>
>> Each time I want to find a package name I do
>> * find -name '*name*' or use github search to locate files in repo.
>>
>> From maintaining perspective:
>>
>> (for x in `ls`; do n=$(ls $x|wc -l);echo "$n - $x";done)|sort -n
>> 1 - backup 2 - inferno 2 - search 3 - gis 4 - display-managers 10
>> - altcoins 11 - science 11 - taxes 20 - virtualization 25 - kde-apps-
>> 15.12 27 - office 41 - version-management 41 - window-managers 42
>> - networking 59 - video 60 - editors 85 - graphics 186 - audio
>> 224 - misc
>>
>> Do you see that? It's hard to define all those categories levels,
>> some of directories have subdirectories (like applications) other not
>> (servers). It's hard to follow. Most people know the name of the
>> software, if not, they probably use google to find it, not using
>> categories.
>>
>> Let's make the layout more clear, more accessible and easy to follow.
>>
>> What do you think about moving all packages into flat namespace?
>>
>> Let's say you have
>>
>> pkgs/package1/default.nix pkgs/package2/default.nix
>>
>> or even better:
>>
>> pkgs/my-package.nix pkgs/gcc.nix pkgs/gcc-5.0.nix
>>
>> then, you can autogenerate top-level.pkgs
>>
>> I'm happy to help implementing that.
>> _
>> nix-dev mailing list nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
> _
> nix-dev mailing list nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev



Links:

  1. https://freshports.org/categories.php
  2. https://freshports.org/categories.php
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Flattening pkgs tree in nixpkgs/pkgs

[Jakob Gillich]

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
> <ja...@gillich.me> wrote:
>> __
>> 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:
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html[1]
>>
>> Maybe this model could work for us, too?
>
> That has 5338 packages in the devel/ folder. I don't think it works.
> Gentoo has a tighter category tree, but they too have run into the
> 1000 files limit:
> https://github.com/gentoo-haskell/gentoo-haskell/tree/master/dev-haskell
> I'm thinking haskell/<2-letter prefix> is the way to go, if we needed
> a separate file for each package. But the current giant-file system is
> fine (other than that GitHub doesn't index it).
>
> -- Mathnerd314



Links:

  1. https://freshports.org/categories.php
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Perl -> C++

[Jakob Gillich]

> 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
enjoy using. At least that's how I personally feel about it, I'm just
not interested in doing any C++ anymore.

On Wed, Jan 6, 2016, at 09:26 PM, Vladimír Čunát wrote:
> On 01/06/2016 06:36 PM, stewart mackenzie wrote:
> > Shall we start defining the nix language?
> 
> None of the perl stuff deals directly with the nix language, so that
> seems rather a much independent issue. Personally, I think there are few
> enough people who contribute to the nix repo as it is now. Do you think
> starting another implementation would help the quality or something
> else? Even in a horizon of up to several years?
> 
> --Vladimir
> 
> 
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
> Email had 1 attachment:
> + smime.p7s
>   5k (application/pkcs7-signature)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Perl -> C++

[Jakob Gillich]

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]: https://doc.rust-lang.org/book/ffi.html


On Thu, Dec 31, 2015, at 12:36 PM, Luca Bruno wrote:
> Nix is already C++. It's just that some tools are written in perl. Nix
> certainly isn't going to be rewritten in another language, at this
> time would be a waste of efforts in my opinion. The perl->c++ is about
> reducing the nix closure even more, but translating perl tools to c++.
>
> On Thu, Dec 31, 2015 at 12:33 PM, Tomasz Czyż
>  wrote:
>> Domen, I think this evolved from why perl -> c++ not perl -> X. Not
>> sure this went to nix -> X. But if decision was already made that c++
>> is the one, probably discussion is over :)?
>>
>
> _
> nix-dev mailing list nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Configure WiFi networks for NetworkManager in configuration.nix?

[Jakob Gillich]

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 notebook. I
> struggled somewhat, especially with network configuration, but in the
> end I managed to configure it using network-manager and "nmcli".
>
> I'd much prefer if I could pre-configure all my default WiFi networks
> for network-manager via configuration.nix, instead of having to set
> them up manually with nmcli. Is that possible?
>
> If it's not possible, I'd like to try contributing such a feature to
> the network-manager package in nixpkgs. Would such a contribution be
> accepted? What API (i.e. example nix expression) would you like to see
> for that, or should I propose one? From some quick reading on the
> Internet, I believe NetworkManager keeps its settings as files in 
> /etc/NetworkManager/system-
> connections/ [1]; if I'm right on that, I assume I should create such
> files from the nix-expression; does that sound correct?
>
> [1]: https://wiki.gnome.org/Projects/NetworkManager/SystemSettings
> Thanks, /Mateusz.
> _
> nix-dev mailing list nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] nixos-in-place - Install NixOS on top of any Linux distro

[Jakob Gillich]

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 DigitalOcean, and other VPS providers,
> I've created https://github.com/jeaye/nixos-in-place
> 
> nixos-in-place can be used for other purposes, outside of VPSs, for
> installing NixOS on top of any existing distro. However, where it shines
> is converting existing VPSs into NixOS without any live media.
> 
> I know there's a great deal of work being done, by aszlig, on the
> nixos-assimilate project which covers much of the same ground as
> nixos-in-place. Currently, nixos-assimilate isn't usable; however, once
> it is, I do believe there won't be a need for nixos-in-place anymore.
> nixos-assimilate appears to be a much more complete solution and will
> likely result in a much more nix-y experience.
> 
> Until then, with love, I hope the NixOS community is able to enjoy NixOS
> systems on providers which otherwise would have more limited options.
> 
> nixos-in-place is very new software; please take any issues or requests
> to the Github issue tracker. Feel free to ping me in IRC.
> 
> Cheers,
> Jeaye
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] How to write module outside the nixpkgs tree and integrated with nixos-rebuild

[Jakob Gillich]

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 short. The manual
   entry is much better, I'm not sure why this page even exists.
3. NixOps

The current manual is nowhere to be found, probably because it's just a
single page and gets outranked by pages that have the keywords higher
up. Maybe providing both the single page and the sections split to
single pages would improve that (that's how FreeBSD does it).


On Fri, Dec 4, 2015, at 07:08 PM, Layus wrote:
> Oh, it seems that you misunderstood me.
>
>
  My point is that that particular information (i.e. "How to add
  custom modules?") is not easy to find in the docs/wiki.
>
  I claim this based on the (relatively) big number of users asking
  that question on the mailing list and at NixCon.
>
>
  So I asked you to give examples of places where you looked for
  that piece of information (wiki, nixos man, eetc ?), and how you
  looked for it (google, nixos options, nixos.org search? what
  keywords you used, etc.).
>
  That way, I would know where to add the required explanations to
  help future users facing the same question.
>
>
  G.
>
>
  On 04/12/15 18:26, rohit yadav wrote:
>> Yes,
  it was mistake on my part. In NixCon someone proposed to
  remove the current wiki because it is outdated. But I guess I
  should first try before asking. I will post questions with
  more caution in future.
>>
>> -Rohit
>>
>> On Fri, Dec 4, 2015 at 2:39 AM,
  Guillaume Maudoux (Layus)  wrote:
>>> This is not the first
  time this question arises on the mailing list.
>>>
>>>
  Where did you expect to find this information in the docs
  ?
>>>
  This may be the ideal place to add the info.
>>>
>>>
  G.
>>>
>>> Le 04/12/15 06:18, rohit yadav a écrit :
 Thanks!

This is exactly I was looking for. I should have
looked more before posting this query.

 --
 Rohit

 On Thu, Dec 3, 2015 at
10:14 PM, Игорь Пашев
 wrote:
> 2015-12-04 6:12
GMT+03:00 rohit yadav
:
>
> Hi,
>
>
>
> How to write a NixOS module that is
outside the nixpkgs tree and integrate
>
> it with nixos-rebuild. I particularly
want to define few services which
>
> should be run in a particular order. I
believe I can define them directly in
>
> /etc/systemd/system folder (but this
defeats the purpose of nix).
>
>
>
> Use imports = [  ];
  in /etc/nixos/configuration.nix
>
> https://nixos.org/wiki/NixOS:extend_NixOS



 ___
nix-dev mailing list
 nix-dev@lists.science.uu.nl
 http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>>
>>>
>>>
___
>>>
nix-dev mailing list
>>> nix-dev@lists.science.uu.nl
>>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>>
>>
>
> _
> nix-dev mailing list nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev