[Nix-commits] [NixOS/nixpkgs] b1ffe5: lib/generators: toPretty

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: b1ffe5e4c029c9f5675bcc42997413fd1b21fbf1
  
https://github.com/NixOS/nixpkgs/commit/b1ffe5e4c029c9f5675bcc42997413fd1b21fbf1
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M lib/generators.nix
M lib/tests/misc.nix

  Log Message:
  ---
  lib/generators: toPretty

`toPretty` implements a pretty printer for nix values.


  Commit: feb8cbdc38c6b10b2c66a96151d8d560e960c29f
  
https://github.com/NixOS/nixpkgs/commit/feb8cbdc38c6b10b2c66a96151d8d560e960c29f
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M lib/debug.nix

  Log Message:
  ---
  lib/debug: traceSeqN & traceSeqValN

Strict trace functions that only go down to a specified depth.
Handy to get a better picture and prevent infinite recursions.


  Commit: 5cbc6ca9bb63f939dab2c2c82a63d72f1f30d9b7
  
https://github.com/NixOS/nixpkgs/commit/5cbc6ca9bb63f939dab2c2c82a63d72f1f30d9b7
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-06-22 (Thu, 22 Jun 2017)

  Changed paths:
M lib/generators.nix
M lib/tests/misc.nix

  Log Message:
  ---
  lib/generators: put more information in toPretty lambdas

With `builtins.functionArgs` we can get some information if the first argument
is an attrset and whether the contained fields have default values. Encode that
into the pretty-printed lambda.


Compare: https://github.com/NixOS/nixpkgs/compare/dd3f2e648a6e...5cbc6ca9bb63___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 79dd4d: Ultrastar (#26524)

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 79dd4deda5a5ee44359a88cdcbbc22a15ba26224
  
https://github.com/NixOS/nixpkgs/commit/79dd4deda5a5ee44359a88cdcbbc22a15ba26224
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-06-14 (Wed, 14 Jun 2017)

  Changed paths:
A pkgs/build-support/plugins.nix
A pkgs/development/libraries/audio/libbass/default.nix
A pkgs/games/ultrastardx/1.1.nix
A pkgs/games/ultrastardx/1.3-beta.nix
R pkgs/games/ultrastardx/default.nix
M pkgs/tools/audio/beets/default.nix
A pkgs/tools/misc/ultrastar-creator/default.nix
A pkgs/tools/misc/ultrastar-manager/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  Ultrastar (#26524)

* ultrastardx-beta: init at 1.3.5

* libbass, libbass_fx: init at 24

* ultrastar-creator: init at 2017-04-12

* buildSupport/plugins.nix: add diffPlugins

Helper function to compare expected plugin lists to the found plugins.

* ultrastar-manager: init at 2017-05-24

The plugins are built in their own derivations, speeding up (re-)compilation.
The `diffPlugins` function from `beets` is reused to test for changes in the
plugin list on updates.

* beets: switch to diffPlugins

The function is basically just extracted for better reusability.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-dev] A nix pretty-printer and a trace function you can tell how deep it should go

[Profpatsch]

https://github.com/NixOS/nixpkgs/pull/26433

Pretty Printing:

nix-repl> lib.generators.toPretty {} { foo = [ 2 3 netcat-openbsd ]; bar = 
lib.id; x = {args, def ? 42}: args; }
"{ \"bar\" = <λ>; \"foo\" = [ 2 3 <δ> ]; \"x\" = <λ:{args,(def)}>; }"

nix-repl> lib.generators.toPretty {} (import )
"<λ:{(config),(crossSystem),(localSystem),(overlays),(platform),(system)}>"


Trace Folding:

nix-repl> foo = { a = [ 1 [ 2 3 ] ]; b = { c.d.e = "yip yip"; }; }

nix-repl> lib.traceValSeqN 10 foo
trace: { "a" = [ 1 [ 2 3 ] ]; "b" = { "c" = { "d" = { "e" = "yip yip"; }; }; }; 
}
{ a = [ ... ]; b = { ... }; }

nix-repl> lib.traceValSeqN 3 foo
trace: { "a" = [ 1 [ 2 3 ] ]; "b" = { "c" = { "d" = {…}; }; }; }
{ a = [ ... ]; b = { ... }; }

nix-repl> lib.traceValSeqN 1 foo
trace: { "a" = […]; "b" = {…}; }
{ a = [ ... ]; b = { ... }; }

nix-repl> lib.traceValSeqN 0 foo
trace: {…}
{ a = [ ... ]; b = { ... }; }


https://twitter.com/Profpatsch/status/874127956884566016

I hope this helps some people.
Please review the code.


-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Camp++ 0x7e1, 6.–9. July, Komárom, Hungary

[Profpatsch]

Since it came up on IRC:
There will be a very cool HACK camp next month
https://camp.hsbp.org/2017/pp7e1/

Everyone brings what they can and a tent,
and we just nerd around for a few days.
No obligations, no schedule, awesome folks.

to whom it may concern

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra and security updates

[Profpatsch]

On 17-06-04 12:35am, Nicolas Pierron wrote:
> So currently, this project is held by a dead-lock between people
> asking me to demonstrate a large scale example, and having the
> infrastructure to doing so.

I think most of the lockup stems from people
not really knowing what your framework means in practice.

Would you be willing to do a talk about that
(and the remaining work tbd) on Nixcon?

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Evaluation time vs build time

[Profpatsch]

On 17-05-31 08:07pm, Linus Heckemann wrote:
> On 31/05/17 18:01, Judson Lester wrote:
> As far as I understand it, it's mostly true — I believe it *is* actually
> possible, just strongly discouraged and absolutely not accepted in
> nixpkgs because (iiuc) of the mess of dependencies it can create.

That is true.

something like
```
let
  fooSrc = fechgit {};
  fooDerivation = import "${fooSrc}/default.nix"
in
  fooDerivation
```

will build the fooSrc derivation at *evaluation time*
(blocking the evaluator) before building the derivation
imported from the fooSrc derivation output.

Because the hash of `fooSrc` has to be given,
the default.nix in `fooSrc` is also fixed-input.

It is strongly discouraged in nixpkgs,
though I sometimes use it for private projects.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Auto-generated expressions for applications

[Profpatsch]

On 17-05-31 08:25am, Benno Fünfstück wrote:
> A package set
> is a consistent set of packages of a given language.

exactly that is not possible with e.g. npm or golang packages.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Node example?

[Profpatsch]

On 17-05-31 08:29am, Benno Fünfstück wrote:
> the reason it works on your test machine but doesn't work on CI is probably
> because of build sandboxing (see `build-use-sandbox` nix option: that
> disables network access & access to certain FS paths for nix builders).

btw can we please finally enable sandboxing by default?
That would be nice thx.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Auto-generated expressions for applications

[Profpatsch]

On 17-05-30 08:02am, Wout Mertens wrote:
> This actually ties into my question about nodePackages. It seems to me that
> for these large packaging systems, we should have separate repos that
> update from their source, and you can then include them into your nixpkgs
> configuration.

nodePackages is a bad example, because “node dependencies”
make no sense on their own. Each application brings with
it its own set of dependencies.

> 
> Only packages that are useful by themselves should get a derivation in
> nixpkgs, the rest would be in these add-on repos. For nodejs, that would be
> e.g. yarn.
> No idea how to accomplish this though.

Exactly.
As long as we keep generated formats in nice, diffable formats
they shouldn’t impose too much noise to the system.
Unfortunalely, the current output of node2nix is quite verbose.

As far as CVEs go, one would have to integrate sites like
https://snyk.io/vuln somehow.


-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] 3fa1be: Add `isStorePath` tests (#26223)

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 3fa1be6f491d9f3ce359234aa1e479e6d91a598f
  
https://github.com/NixOS/nixpkgs/commit/3fa1be6f491d9f3ce359234aa1e479e6d91a598f
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-05-30 (Tue, 30 May 2017)

  Changed paths:
M lib/tests/misc.nix

  Log Message:
  ---
  Add `isStorePath` tests (#26223)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 2b0a84: lib/string: make `isStorePath` total (#26216)

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 2b0a8427e6995eefddf09919ad48a7887e65
  
https://github.com/NixOS/nixpkgs/commit/2b0a8427e6995eefddf09919ad48a7887e65
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-05-30 (Tue, 30 May 2017)

  Changed paths:
M lib/strings.nix

  Log Message:
  ---
  lib/string: make `isStorePath` total (#26216)

fix #9278


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Python: Provide your own buildPhase and installPhase.

[Profpatsch]

On 17-05-26 09:03pm, Nawal Husnoo wrote:
> Hi,
> 
> Could anyone point me to an example where I can see this in action please?

Just use grep on the nixpkgs,
you will find many examples.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nixos wiki project

[Profpatsch]

On 17-05-16 09:52pm, Jos van den Oever wrote:
> On Friday 12 May 2017 20:36:59 Matthias Beyer wrote:
> > On 10-05-2017 10:52:16, Arseniy Seroka wrote:
> > > I think that disabling wiki is one of the the worst
> > > decisions in nixos community.
> > 
> > +1
> 
> I think it's unfortunate that a free software project chooses a closed 
> platform to do development. GitHub is not even open core like GitLab.

Didn’t we have a FAQ somewhere
where these decisions are explained?

If not, it should probably go into the Wiki. :D

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] why has each revision / generation not a own configuration.nix

[Profpatsch]

On 17-05-16 04:43pm, zimbatm wrote:
> How do you find back which git revision was used to produce a given NixOS
> profile?

In my case it’s built by a hydra and the system name contains a hash.

> 
> Maybe nixos-rebuild should be extended to include that in the revision
> name, and if the git repo is dirty.

You need to include all used paths.
So it’s probably best to write out a file like:

- : 
source: /home/philip/vuizvui
type: git
git:
  dirty: yes
  rev: 32847298abc
hash:
  type: sha256
  hash: deadbeef

- :
source: https://cache.nixos.org/…/nixpkgs.tar.gz
type: tgz
tgz:
  …
hash:
  …

- system:
source: user@machine
type: arg
arg:
  type: string
  val: "x86_64-linux"


Something like that.
YAML because I had to write it by hand.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] 685bfc: fira-code-symbols: init at 20160811

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 685bfcee633774d730cd3da2fba6eb39a1b767b9
  
https://github.com/NixOS/nixpkgs/commit/685bfcee633774d730cd3da2fba6eb39a1b767b9
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-05-16 (Tue, 16 May 2017)

  Changed paths:
A pkgs/data/fonts/fira-code/symbols.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  fira-code-symbols: init at 20160811


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Declarative VMs in libvirt/Qemu

[Profpatsch]

On 17-05-15 07:26pm, Justin Humm wrote:
> Hello everyone,
> 
> I'm looking for a best practice for declarative VMs in libvirt/qemu. What I 
> want
> to do:

Might be of interest https://github.com/NixOS/rfcs/pull/12


-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] why has each revision / generation not a own configuration.nix

[Profpatsch]

On 17-05-13 12:25pm, Layus wrote:
> On 13/05/17 12:14, Leo Gaspard wrote:
> See the previous ML discussion on that topic where we proposed to keep it
> opt-in, but with an apt-out config line in the default configuration.nix.
> This may already be implemented.

The ones who don’t keep their sources under version control 
deserve their eventual fate.

Seriously, copying & pasting default templates around
is not a good idea.
I haven’t seen a “default” configuration.nix (whatever that is)
in more than 1.5 years.

We already have the firewall enabled by default,
even that has been a major discussion,
because for everything that is implicit
you have to remember to turn it off.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] How to incorporate my Bash script in configuration.nix

[Profpatsch]

On 17-05-12 05:02pm, Profpatsch wrote:
> systemd.service.myUsbService = 
>   let startupScript = ''
> #!${pkgs.bash}
> echo "0b05 17e8" | tee /sys/bus/usb/drivers/rt2800usb/new_id
>   '';
>   in { 
> description = "get my US WiFi to work";
> wantedBy = [ "default.target" ];
> serviceConfig = {
>   ExecStart = startupScript;
> };
>   };

aszlig just told me that this can be done shorter:

systemd.service.myUsbService = {
  description = "get my US WiFi to work";
  bindsTo = [ "sys-subsystem-net-devices-XXX.device" ];
  script = "echo 0b05 17e8 | tee /sys/bus/usb/drivers/rt2800usb/new_id";
}

see `man systemd.device`.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] How to incorporate my Bash script in configuration.nix

[Profpatsch]

On 17-05-08 02:28pm, Strahinja Popovic wrote:
> Hi everyone,
> 
> I have made my USB WiFi to work,
> but I have to call this script whenever I restart the computer.
> 
> #!/usr/bin/env bash
> echo "0b05 17e8"|sudo tee /sys/bus/usb/drivers/rt2800usb/new_id
> 
> What is correct way to make this part of configuration.nix?

probably by adding service file to bootup, like:

systemd.service.myUsbService = 
  let startupScript = ''
#!${pkgs.bash}
echo "0b05 17e8" | tee /sys/bus/usb/drivers/rt2800usb/new_id
  '';
  in { 
description = "get my US WiFi to work";
wantedBy = [ "default.target" ];
serviceConfig = {
  ExecStart = startupScript;
};
  };

Maybe you’ll have to play with the units it needs to run before.
I point you to `man configuration.nix` and `man systemd.unit`.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nixos wiki project

[Profpatsch]

On 17-05-10 07:56am, Mic92 wrote:
> As the official wiki is now finally part of the history: 
> https://nixos.org/nixos/wiki.html,
> we have started our own community wiki:
> 
>   https://github.com/nixos-users/wiki/wiki
> 
> It is at the moment editable by every GitHub user and
> we use our IRC channel #krebs to review and track changes.

fyi, at the NixOS hackathon $Person
(which can reveal herself if they so choose)
tried to revive the official Mediawiki by enabling Github auth.

It didn’t succeed that day,
but in principle that should make the official Wiki usable again.

Alternatively simply declare the GH-Wiki the official one.
Pros: Markdown, Git repo, Github integrated
Cons: I can’t think of any

Of course set wiki.nixos.org to a 300 Redirect.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] still waiting for https://cache.nixos.org after 5 seconds...

[Profpatsch]

On 17-05-08 07:08am, Graham Christensen wrote:
> Our cloudfront distribution sees almost almost 100,000 unique users each
> month, each downloading hundreds or thousands of NARs and narinfo files.
> At the size of the cache (many TBs) and traffic it sees, these numbers
> aren't an easy feat.

By now I’m pretty sure the nix 1.11 networking code
is a bit flaky at times, especially the timeout & retry logic.

I heard it was rewritten for 1.12, is that right?

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] How to escape $'\t' in Nix multi-line string?

[Profpatsch]

On 17-04-30 03:07pm, Bjørn Forsman wrote:
> On 30 April 2017 at 15:01, Bjørn Forsman  wrote:
> > Hi all,
> >
> > I'm stuck trying to pass $'\t' to bash via Nix multi-line strings:
> >
> > nix-repl> ''cut -d $'\t' -f 1''
> > error: syntax error, unexpected $undefined, expecting IND_STR or
> > DOLLAR_CURLY or IND_STRING_CLOSE, at (string):1:10
> 
> Oh, it was only missing double single-quotes before the dollar sign.
> 
> What tripped me was that the documentation says ${ is special in
> strings, not $'.

How should we improve the manual in this regard?

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] For go-wizards: Building the geth using buildGoPackage

[Profpatsch]

On 17-04-26 12:18pm, Sergey Mironov wrote:
> Upstream maintainer pointed out to
> https://github.com/golang/go/issues/14669 problem. I've tried adding
> 
> preBuild=''
>   export CGO_CFLAGS='-O0'
> '';
> 
> without success..

You will have to poke a bit.

I’d read the definition of `buildGoPackage` now,
which can be found in
`pkgs/development/go-modules/generic/default.nix`.

Another idea would be preConfigure = "set -x"
to make bash output everything it calls.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Simplify node packages?

[Profpatsch]

On 17-04-25 12:21pm, Sander van der Burg wrote:
> I'm not sure if you have read my blog articles correctly, but what node2nix
> currently does is one derivation per application and statically bundles all
> NPM dependencies with it. The old approach that npm2nix used to implement
> was a derivation per dependency and symlinking between them. As explained
> in this blog post:
> http://sandervanderburg.blogspot.com/2016/02/managing-npm-flat-module-installations.html
> this works for many packages, but does not reliably work in all cases.
> Moreover, it does not work with packages having cyclic dependencies.

Apart from cyclic dependencies and leaving out “flattened” trees,
are there any other deal-breakers you can think of?

> Now yarn (and other approaches such as ied) do obviously a much better job
> than NPM in some aspects. Unfortunately, as of today, NPM remains the
> de-facto standard for Node.js package deployment, and I'm not sure if this
> will ever change.

yarn is pretty much a drop-in replacement for npm.
Instead of `npm install && node2nix` you say `yarn install && yarn2nix`
and you get a local `node_modules` and in yarn’s case also a `yarn.lock`.

So as far as packaging goes, adoption should not matter imho.

> The latter aspect can only be solved if NPM makes their dependency
> addressing and composition facilities better.

+1 

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Simplify node packages?

[Profpatsch]

On 17-04-25 08:20am, Benno Fünfstück wrote:
> If we get upstream to support enough for our use case, the solution should
> be much more stable.

Upstream support might be helpful,
but that’s a wholly different beast.

> Hmm, so perhaps in we can unpack the tarballs already in `phase 1` and tell
> yarn to just look in $DIR for unpacked tarballs? Yarn should already have
> most of the code that is required for correct symlinking, no?

The code for correct symlinking is <4 lines,
maybe a few more for manpages and binaries.

I’d argue integrating it into yarn is even more frickle:
1. With yarn there’s now two implementations of npm packages.
2. We have to invest into lobbying so our integration
   isn’t broken by upstream sometimes. Then lobby again.
3. You’d definitely have to change yarn to have
   an offline mode where it doesn’t try to download stuff.
   I’m pretty sure upstream doesn’t care about that very much.

These are the problem points I see.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Simplify node packages?

[Profpatsch]

On 17-04-25 07:26am, Benno Fünfstück wrote:
> >
> > The most interesting property is, that all dependency trees
> > are linked together with symlinked, so they are cached by nix
> > on a package level:
> > https://github.com/Profpatsch/yarn2nix/blob/master/buildNodePackage.nix#L33
> 
> 
> Does this caching really gain us that much? The disadvantage of doing this
> is that we have to maintain our own scripts for doing it, since upstream
> does not support it.

Depends by who you mean by upstream.

yarn: only the parser could break, but that’s easily fixable
npm: they could change something in how packages work,
but that’s unlikely.

> phase 1: build a directory full of tarballs (just symlink the result of
> fetchurl without unpacking)
> phase 2: let yarn assemble the dependency tree (thus it will deal with
> cyclic dependencies for us)

Right now it takes around 4–5 minutes to unpack the tarballs
for my project with node2nix. That is on every dep change.

> This would only need a feature from upstream to use cached tarballs.

npm uses the following algorithm:
1. resolve dependencies
2. move dependencies as far up the tree as possible to enable sharing
3. unpack the tarballs into the correct dirs
4. link the "bin" files into a .bin directory and the man files

That’s it.
We can skip step 2, because we don’t copy, but symlink
already extracted packages (and filename length is not
a problem on modern ext/btrfs/zfs)
Step 4 becomes trivial once we skip 2.

yarn is really just a 1:1 rewrite of node with lockfiles.
I don’t know why people celebrate it so much,
because it does exactly nothing differently apart from
creating the lockfiles.
Don’t even know why a rewrite was necessary.

Maybe I missed something, but that’s the plan.

-- 
Proudly written in Mutt with Vim on NixOS.
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Simplify node packages?

[Profpatsch]

On 17-04-23 01:10pm, Benno Fünfstück wrote:
> * A simple approach to packaging NPM applications would be to split the
> package for an NPM application into two:
>   - fetch: let NPM download all the dependencies. it should(?) be possible
> to make this a fixed-output derivation, as long as NPM downloads the same
> set of dependencies each time
>   - build: use the cache from the fetch phase, should require no network
> access
> 
> The fetch phase should be deterministic if we freeze the NPM index (is such
> a thing possible?) and use shrinkwrap.
> Or is this not the case? In what cases will it fail to be deterministic?
> 
> * Alternatively, `yarn` claims to be more deterministic. Can we use `yarn`
> to build all NPM packages? Or are there NPM packages that are incompatible?

I’m in the process of writing yarn2nix.

After resolving dependencies yarn writes a lockfile,
example: https://github.com/facebook/react/blob/master/yarn.lock
As you can observe this has everything we need (even the hash!)

Sadly it is not a known format, so I wrote a simple-stupid parser:
https://hackage.haskell.org/package/yarn-lock-0.1.0/docs/Yarn-Lock.html

The pre-alpha-version of converting yarn.lock files to nix expressions
can be found here:
https://github.com/Profpatsch/yarn2nix

nix-shell
$ hpack
$ cabal build
$ ./dist/build/yarn2nix/yarn2nix

should do the trick.

It works for simple yarn.lock files, but the generated output
cannot be nicely checked in yet, since it’s way too verbose.
I need to change the internal data representation a bit,
to a multi-keyed map.

When trying to build our production (ember) app I stumbled on
another major problem: npm package dependencies and yarn.lock
files have cycles.
No sane package manager would allow cycles, but here we are.
So a cycle-breaking function is still needed, not very much
work but not trivial either.

The most interesting property is, that all dependency trees
are linked together with symlinked, so they are cached by nix
on a package level:
https://github.com/Profpatsch/yarn2nix/blob/master/buildNodePackage.nix#L33

I expect yarn2nix to be ready in a few days, most certainly
in the next two weeks.

-- 
Proudly written in Mutt with Vim on NixOS.
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOps reproducible bug with large amount of deployment.keys

[Profpatsch]

On 17-04-19 12:27pm, 4levels wrote:
> The main reason is that the keys derivation contains all key related
> statements on a single line and is passed as a single argument to bash,
> triggering the maxlength error (argument list too long).  I could reduce
> the lenght of the names of the keyfiles, since this will actually reduce
> the total length of the generated keys derivation, but that's no solution,
> especially since I'm intending to deploy even more keys in the near future..

Can you link to the line where bash is called
with too many arguments?

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Postgresql, rsyslog and systemd journal

[Profpatsch]

On 17-04-19 04:08pm, Danylo Hlynskyi wrote:
> 
> in psql session.
> 
> The problem is, logs still are routed to systemd journal, not to configured
> `rsyslog`.

journald (rightfully!) captures calls to the syslog(3) function.

For further inquiries visit your local manpages.
man 8 systemd-journald.service


-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] For go-wizards: Building the geth using buildGoPackage

[Profpatsch]

On 17-04-19 09:50pm, Sergey Mironov wrote:
> building the geth

I had a short fear of sentinent AI robots, but it’s (just?)
a go package.

> # github.com/ethereum/go-ethereum/vendor/github.com/karalabe/hid
> go/src/github.com/ethereum/go-ethereum/vendor/github.com/karalabe/hid/wchar.go:44:8:
> error: enumerator value for '__cgo_enum__0' is not an integer constant
>return stringToWchar4(s) // Unix
> ^

That’s normal go compile errors.
Are you using a very old version of the go compiler?

Have you tried building it on unstable/master?
You can check out nixpkgs with git
and run `nix-build -A ` from there.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOps failes to deploy: bash: Argument list too long

[Profpatsch]

On 17-04-15 10:14am, 4levels wrote:
> Hi Profpatsch,
> 
> the name nixos-system-secure comes from one machine called "secure".
> I'm using various nix files to separate / group some parts of the machine
> configurations we're using.
> We're deploying +10 servers for our application code (mancloud) and the
> machine with name "secure" is supposed to have all keys from all other
> machines on it.
> 
> I don't see where I should add the mentioned `set -x`
> We're usually calling nixops as follows
> nixops deploy --include secure --build-only -I nixpkgs=
> https://github.com/NixOS/nixpkgs-channels/archive/nixos-16.09.tar.gz
> 
> …

I’m pretty sure you are not well-versed with nix and nixos yet.
nixops builds on these two blocks.

https://nixos.org/nix/manual/
https://nixos.org/nixos/manual/

Once you work through these manuals
most of your questions will be answered.


-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] 7df8e5: psc-package: init at 0.1.1

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 7df8e53d288915d2623479e117ce3c855bc3df7c
  
https://github.com/NixOS/nixpkgs/commit/7df8e53d288915d2623479e117ce3c855bc3df7c
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-04-15 (Sat, 15 Apr 2017)

  Changed paths:
A pkgs/development/compilers/purescript/psc-package/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  psc-package: init at 0.1.1


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] NixOps failes to deploy: bash: Argument list too long

[Profpatsch]

On 17-04-14 09:44pm, 4levels wrote:
> Hi Profpatch,
> 
> Thanks for your reply, but I don't know how to even try implementing your
> suggestions. This file is generated by NixOps and is run just before the
> actual deployment starts. This is at the end of the build phase before the
> actual deploy. It starts with
> 
> Derive([("out","/nix/store/j9p5zwqj03nq4f4id5a0phig5gk0snqd-nixos-system-secure-16.09pre-git","","")],
> ...

This is a derivation.
They are normally generated by nix expressions,
mostly out of the nixpkgs repo.

nixos-system-secure looks like a system derivation
created somewhere in nixpkgs/nixos.
You might try searching for nixos-system-secure.
In this case nixos-system leads you to the correct file.
`buildCommand` is the build description. It is aliased
above as `systemBuilder`. Try adding `set -x` into it
and start nixops with your nixpkgs (man nixops, search for -I).

`-I` is kind of stateful with nixops,
so you might want to build that machine with nix-build first.
nixpkgs/nixos/default.nix, concrete:

nix-build -A vm \
  -E 'import /path/to/nixpkgs/nixos { configuration = 
/path/to/machine/configuration; };'

Hope that helps finding the bug.

> 
> I have literally no idea where to look or what to change in NixOps itself
> to use the suggestions you made, as this goes way beyond my nix-knowledge.
> For all I know, this issue could come from something totally different as
> well, I'm just gessing here since this is the last output of the nixops
> deploy call before the error message. Below the full output of the call
> 
> [erik@no01:~]$ nixops deploy --build-only --show-trace
> building all machine configurations...
> these derivations will be built:
> 
> /nix/store/wz9mvb6x082h4mvww1gsf0x0l9fq8p7z-nixos-system-secure-16.09pre-git.drv
>   /nix/store/bz3ajdlxalr0c8i1zik40zwvnsb2g8a7-nixops-machines.drv
> building path(s)
> ‘/nix/store/j9p5zwqj03nq4f4id5a0phig5gk0snqd-nixos-system-secure-16.09pre-git’
> while setting up the build environment: executing
> ‘/nix/store/gabjbkwga2dhhp2wzyaxl83r8hjjfc37-bash-4.3-p48/bin/bash’:
> Argument list too long
> builder for
> ‘/nix/store/wz9mvb6x082h4mvww1gsf0x0l9fq8p7z-nixos-system-secure-16.09pre-git.drv’
> failed with exit code 1
> cannot build derivation
> ‘/nix/store/bz3ajdlxalr0c8i1zik40zwvnsb2g8a7-nixops-machines.drv’: 1
> dependencies couldn't be built
> error: build of
> ‘/nix/store/bz3ajdlxalr0c8i1zik40zwvnsb2g8a7-nixops-machines.drv’ failed
> error: unable to build all machine configurations
> 
> 
> Kind regards,
> 
> Erik
> 
> 
> On Fri, 14 Apr 2017, 22:00 Profpatsch, <m...@profpatsch.de> wrote:
> 
> > On 17-04-14 02:26pm, 4levels wrote:
> > > I think this is the generatd file causing the issue:
> > >
> > /nix/store/wz9mvb6x082h4mvww1gsf0x0l9fq8p7z-nixos-system-secure-16.09pre-git.drv
> > > It looks like it's a single line of code, spanning 207073 characters,
> > which
> > > is pbbly more than the allowed argument length for bash.
> > >
> > > Are there any guidelines to avoid running into this argument list error?
> >
> > Depends on your bash use-case.
> > Lots of programs support file-input.
> > xargs may be a good candidate.
> > If you don’t want it sequential, GNU parallel.
> > Or just a plain old bash for; do; done loop.
> >
> > --
> > 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.
> >

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOps failes to deploy: bash: Argument list too long

[Profpatsch]

On 17-04-14 02:26pm, 4levels wrote:
> I think this is the generatd file causing the issue:
> /nix/store/wz9mvb6x082h4mvww1gsf0x0l9fq8p7z-nixos-system-secure-16.09pre-git.drv
> It looks like it's a single line of code, spanning 207073 characters, which
> is pbbly more than the allowed argument length for bash.
> 
> Are there any guidelines to avoid running into this argument list error?

Depends on your bash use-case.
Lots of programs support file-input.
xargs may be a good candidate.
If you don’t want it sequential, GNU parallel.
Or just a plain old bash for; do; done loop.

-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] What's the "perfect setup" for hacking on Nix?

[Profpatsch]

On 17-04-11 09:28pm, Chris Marusich wrote:
> Since Nix is implemented in C++, I guess any
> C++ IDE (or modes/tools in emacs) would be helpful.  I was just curious
> to know if any particular IDE or technology was heavily used by the Nix
> community.

You normally don’t have to know any C++ for most tasks.
Working on the package manager itself is the smallest part,
nearly all of the work is done in nixpkgs,
that is: with nix expressions and lots of (bash) scripts.


-- 
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
https://mailman.science.uu.nl/mailman/listinfo/nix-dev

[Nix-commits] [NixOS/nixpkgs] 048114: compile-daemon: init at 2013-03-08

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 048114eb4f79f3e125dadee106b454e3d72ccdfc
  
https://github.com/NixOS/nixpkgs/commit/048114eb4f79f3e125dadee106b454e3d72ccdfc
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-04-12 (Wed, 12 Apr 2017)

  Changed paths:
A pkgs/development/tools/compile-daemon/default.nix
A pkgs/development/tools/compile-daemon/deps.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  compile-daemon: init at 2013-03-08


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 9b7b95: /lib/default.nix: Add file docstring & unit test h...

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9b7b950832e6ae97c301e8328b797e8b39efb545
  
https://github.com/NixOS/nixpkgs/commit/9b7b950832e6ae97c301e8328b797e8b39efb545
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-04-12 (Wed, 12 Apr 2017)

  Changed paths:
M lib/default.nix

  Log Message:
  ---
  /lib/default.nix: Add file docstring & unit test hint


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] What's the "perfect setup" for hacking on Nix?

[Profpatsch]

On 17-04-08 11:17pm, Chris Marusich wrote:
> Hi Nix devs!
> 
> What is the "perfect setup" for hacking on Nix?  Is there an IDE that
> the you prefer to use?  Is there a C++ major mode for Emacs that you
> can't live without?  Are there other helpful tools?

A very good text editor. I can recommend Spacemacs.
nix comes with a `nix-mode.el` file for Emacs.
On Spacemacs, there is the `nixos` layer
which is nice, if rudimentary.

Since nix is a relatively new DSL, the editor-support is lacking.
Compared to Scheme at least.

I recommend studying the nix-* tools in-depth, they are your
main user interface. Particularly nix-store, nix-instantiate, nix-build.
Also, nix-repl is very helpful (separate package).

-- 
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

Re: [Nix-dev] Is CI of pull requests broken?

[Profpatsch]

On 17-04-08 11:19pm, Volth wrote:
> I noticed that many pull requests [1] have failed Travis CI tests.
> The reasons of failures are often very strange, especially if the
> change introduced by PR looks innocent: some "file not found" or
> "build times out".
> 
> Moreover, many of the merged pull requests [2] also have failed CI. It
> looks like the failed CI signal nothing to the people who do merge.
> Everybody just knows that CI is broken and its success or failure
> means nothing. Is it so?

Pretty much.

-- 
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-commits] [NixOS/nixpkgs] 6b5e5d: rss2email: init at 3.9

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 6b5e5de0ef2a040cab9af7388487b16030b877db
  
https://github.com/NixOS/nixpkgs/commit/6b5e5de0ef2a040cab9af7388487b16030b877db
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-04-05 (Wed, 05 Apr 2017)

  Changed paths:
A pkgs/applications/networking/feedreaders/rss2email/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  rss2email: init at 3.9


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] paths in user's i3 configs broken by upgrade

[Profpatsch]

On 17-04-03 04:25pm, Mark Gardner wrote:
> Instead of:
> 
> bindsym $mod+d exec
> /nix/store/04sx6lx7hssid7a6iwdbdvxbkp25xsx1-dmenu-4.6/bin/dmenu_run
> 
> I think it should be to be:
> 
> bindsym $mod+d exec /run/current-system/sw/bin/dmenu_run

The problem with /run/current-system is
that it’s nixOS only.
The package should work on e.g. Darwin as well.

So probably use `/usr/bin/env dmenu_run` and similar.

-- 
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-commits] [NixOS/nixpkgs] a1e617: modules/searx: fix configFile type

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: a1e6176cbf3b38cf2ecc8f1543d6c562f509a144
  
https://github.com/NixOS/nixpkgs/commit/a1e6176cbf3b38cf2ecc8f1543d6c562f509a144
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-04-04 (Tue, 04 Apr 2017)

  Changed paths:
M nixos/modules/services/networking/searx.nix

  Log Message:
  ---
  modules/searx: fix configFile type


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Banning people from the mailinglist?

[Profpatsch]

On 17-04-04 10:05am, Matthias Beyer wrote:
> Can we just ban the (non-constructive) "fuck systemd" people? I 
> mean... nobody benefits from this kind of behaviour and it creates 
> frustration all over the place. Nobody gets happy with these kind of 
> messages.
> 
> Is there a technical possibility for this?

Normally these people vent once and then stay quiet;
if someone starts flamewars on a regular basis
we should warn them first, and on repetition ban.

So far that hasn’t happened yet, right?
And maybe these folks will see the light someday. :)


-- 
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

Re: [Nix-dev] [RFC 004] Add Replace Unicode Quotes draft

[Profpatsch]

On 17-03-28 10:03pm, zimbatm wrote:
> Hi everyone,
> 
> RFC 004 is now ready for wider reviews if you care to take a look:
> 
> https://github.com/NixOS/rfcs/pull/4

For posterity, the responses are exactly
the kind of bikeshedding I feared would come out of RFCs.

But maybe it is for the best?
I don’t know.

-- 
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

Re: [Nix-dev] gentoo like nixpkgs globala useflags in nixpkgs config - would it be worth it?

[Profpatsch]

On 17-03-25 11:47pm, Ertugrul Söylemez wrote:
> >> Issue pulseSupport -> does it make sense to have a global 'enable
> >> pulse for all packgages' config.pulseSupport = true flag?
> >>
> >> packages could be using:  config.pulseSupport or false to disable by
> >> default then.
> >
> > In my opinion baking global implicit state into nixpkgs is not a good
> > idea.
> 
> It's not *state*, is it?  We're basically already doing global
> configuration, and I think the proposal is about actually using this to
> get a USE-like system.

Once you have some kind of implicit config file for your user
there is state.

> In other words: please don't turn NixOS into Gentoo by forcing us to
> compile everything. =)

Having hydra compile special versions of your package
is as simple as:

mypkg = callPackage ./my-pkg {}
mypkg-full = callPackage ./my-pkg { someOption = true; };


-- 
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

Re: [Nix-dev] gentoo like nixpkgs globala useflags in nixpkgs config - would it be worth it?

[Profpatsch]

On 17-03-24 03:18pm, Marc Weber wrote:
> Issue pulseSupport -> does it make sense to have a global 'enable pulse
> for all packgages' config.pulseSupport = true flag?
> 
> packages could be using:  config.pulseSupport or false to disable by
> default then.
> 
> Having a defaultFlags = {
>   config.sox = null; # does this cause the package default being used in 
> "config.sox or false" ?
>   config.pulseSupport = null; # please note: you can enable, but most 
> packages will work with pulse without doing so 
>   config.qtSupport = null;
>   config.gtkSupport = null;

In my opinion baking global implicit state into nixpkgs
is not a good idea.

-- 
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

Re: [Nix-dev] Nix for internal projects and monorepos

[Profpatsch]

On 17-03-24 04:01pm, Daniel Peebles wrote:
> How do other people tackle this problem? Does anyone maintain a reasonably
> large internal Nix package set?

The most sensible solution would be to set up
a (private) hydra and add the internal repos to it.
Then you get your channels.


-- 
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] Nix release frequency (was: Re: RFC for RFCs)

[Profpatsch]

On 17-03-23 07:36am, Vladimír Čunát wrote:
> On 03/23/2017 12:58 AM, Bas van Dijk wrote:
> > Strange this has been merged into master over a year ago but it hasn't
> > been released yet. And there have been quite a few releases the last year...
> 
> There have only been maintenance releases 1.11.x since January 2016, and
> most of master code since then is missing from any release.

That’s something that has bothered me for quite a bit.
The releases are not frequent enough; 
in my opinion, nixpkgs master should receive nix updates
*at least* every two months.

There are so many breaking changes in nix “1.12” now
that it’s basically a whole new thing from what I hear.
It should definitely be released as version 2.

I’d urge the nix devteam to move to nix 2 release candidates
on master as soon as possible.


-- 
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

Re: [Nix-dev] how to 'just run binaries' in nixos

[Profpatsch]

On 17-03-22 01:49am, Nikolay Amiantov wrote:
> You may try steam-run. Despite the name it's actually not necessarily
> related to Steam, it just runs binaries in an environment very
> resembling Steam Runtime (which is a good de-facto standard).

There’s also buildEnv from pkgs/build-support/buildenv,
which may be a simpler environment than what steam-run provides.

-- 
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

Re: [Nix-dev] Should we drop 9P?

[Profpatsch]

On 17-03-20 10:27pm, Volth wrote:
> Recently few bugs in 9P were found (#23957 #23020 #22695) which
> reveals that 9P code is not very mature and perhaps NixOS is the first
> team which uses 9P heavily and relies on it in production.

Could you please provide links? 9P is a protocol,
do you mean holes in the protocol have been found?

-- 
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

Re: [Nix-dev] The Church of Suckless NixOS is looking for followers

[Profpatsch]

On 17-03-19 05:55pm, Alexander V. Nikolaev wrote:
> I think we can re-use pre-serialised `systemd.services` attrset, using
> it for emitting plain sysvinit scripts, or runit scripts. And may be
> later introduce new intermediate layer here.

Since (say what you want) systemd service attributes
are mostly quite semantic in their function,
the may already be a fine choice of interface,
even for other init systems/supervisors.

Compare how it is possible to map the kernelmodule
arguments to networkd options:
https://github.com/NixOS/nixpkgs/pull/22388/files#diff-c89412e680a245d4d20968580b84f47dR121

-- 
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

Re: [Nix-dev] How do you work on big packages?

[Profpatsch]

On 17-03-17 05:34pm, Dmitry Kalinkin wrote:
> Also it is funny how your statement is followed by some good advice on how to
> turn nix into even better dev platform. I will only add that one could also
> use ccache to speedup builds:
> 
> my_cool_package.override { stdenv = pkgs.ccacheStdenv; }

Caches will burn you.
You should never mix non-deterministic caching with deployment.
There’s just no way it will work out in all cases.

-- 
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

Re: [Nix-dev] The Church of Suckless NixOS is looking for followers

[Profpatsch]

On 17-03-17 02:00pm, Jan Malakhovski wrote:
> 
> Brothers and Sisters!
> 
> * Our common goal is to have fun (see below) and to get a NixOS system
>   that can run using only suckless tools [1].

I, for one, applaud our new anonymous suckless leaders!
On an offhand note, be advised that suckleast.org is already taken.

> * We like LISP, but we don't think package expressions should be written
>   in LISP just for the sake of LISP. Nor do we like the bloated GNU
>   tools. GuixSD is out of question.

rolf

> We want suckless tools instead of GNU. Sh instead of Bash. Coreboot
> instead of GRUB and BIOS and so on.

gl hf


T. systemd fanboi

-- 
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-commits] [NixOS/nixpkgs] 6da60b: modules/mlmmj: fix a typo in listaddress folder

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 6da60bb10142ba2e63309da048044026f7158d0a
  
https://github.com/NixOS/nixpkgs/commit/6da60bb10142ba2e63309da048044026f7158d0a
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-03-16 (Thu, 16 Mar 2017)

  Changed paths:
M nixos/modules/services/mail/mlmmj.nix

  Log Message:
  ---
  modules/mlmmj: fix a typo in listaddress folder


  Commit: 92bb91f72f649d49bacb55e3b735455d5a740771
  
https://github.com/NixOS/nixpkgs/commit/92bb91f72f649d49bacb55e3b735455d5a740771
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-03-16 (Thu, 16 Mar 2017)

  Changed paths:
M pkgs/servers/mail/mlmmj/default.nix

  Log Message:
  ---
  mlmmj: add docfiles to output


Compare: https://github.com/NixOS/nixpkgs/compare/5d6ea2d64e75...92bb91f72f64___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] how to find packages by file?

[Profpatsch]

On 17-03-15 01:13pm, Linus Heckemann wrote:
> On 14/03/17 20:24, Roni Choudhury wrote:
>  2. Use nix-repl — `nix-repl ''` will give you a REPL for the
> nix language with autocompletion for that sort of thing, which can be
> very helpful.

Can confirm. Normally I use
find /nix/store -iname "*library.so"
to find the package name,
then I grep nixpkgs for that name
then I look at the outputs (whether it’s in `lib` or `out`)
then I grep nixpkgs for the filename to find the attribute name

The naming schemes are pretty similar, it could probably
be automated fairly well.

-- 
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

Re: [Nix-dev] fetchgit

[Profpatsch]

On 17-03-09 04:31pm, Sébastien Petitdemange wrote:
> Hi Profpatsch,
> 
> Yes I'm in the folder where I changed fetchgit but it doesn't call my
> modification version.
> How can I make sure that my package (lima-core) call my modify version?
> Is there a way to do that?

I cannot tell you anything without a patch or at least
a code sample.

-- 
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

Re: [Nix-dev] fetchgit

[Profpatsch]

On 17-03-09 11:52am, Sébastien Petitdemange wrote:
> Hi,
> 
> I've modify fetchgit module to add an optional argument to filter
> submodule. And I would like to use this optional argument to build my
> local package. Unfortunately, nix-build still get fetchgit from the main
> channel instead of ~/local/bcupckgs:
> 
>  -> nix-build  --show-trace ~/local/bcupkgs --cores 8 -A lima-core

If you’re in the folder of the nixpkgs where you changed fetchgit,
it should work. If it doesn’t, maybe your changes are not calling
your modified version of fetchgit.

-- 
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

Re: [Nix-dev] nix-shell with overlay?

[Profpatsch]

On 17-03-08 10:16pm, Nicolas Pierron wrote:
> On Wed, Mar 8, 2017 at 11:01 AM, Benno Fünfstück
>  wrote:
> > Nicolas Pierron  schrieb am Mi., 8. März 2017,
> > 01:30:
> >>
> >> nit: super.callPackage, as the super.callPackage *function* already
> >> aliases self packages.  Otherwise, you would be going twice through
> >> the fix-point.
> >
> > What if someone later wants to override callPackage?
> 
> Later, this person would have to face the fact that security updates
> are not applied.

Ah, it influences security updates.
Is your talk from Nixcon still up-to-date in that respect?

-- 
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-commits] [NixOS/nixpkgs] 9dc3f7: networking/bonds: fix examples

[Profpatsch]

  Branch: refs/heads/release-17.03
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9dc3f75b0b2136e132743de3d4b46d14d15f031a
  
https://github.com/NixOS/nixpkgs/commit/9dc3f75b0b2136e132743de3d4b46d14d15f031a
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-03-08 (Wed, 08 Mar 2017)

  Changed paths:
M nixos/modules/tasks/network-interfaces.nix
M nixos/tests/networking.nix

  Log Message:
  ---
  networking/bonds: fix examples

After the change of the bonding options, the examples were not quite correct.
The diff is over-the top because the new `let` needs everything indented.

Also add a small docstring to the `networkd` attr in the networking test.

(cherry picked from commit 22c265182f9e0d543de0fe46a809180ff2021b85)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 22c265: networking/bonds: fix examples

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 22c265182f9e0d543de0fe46a809180ff2021b85
  
https://github.com/NixOS/nixpkgs/commit/22c265182f9e0d543de0fe46a809180ff2021b85
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-03-08 (Wed, 08 Mar 2017)

  Changed paths:
M nixos/modules/tasks/network-interfaces.nix
M nixos/tests/networking.nix

  Log Message:
  ---
  networking/bonds: fix examples

After the change of the bonding options, the examples were not quite correct.
The diff is over-the top because the new `let` needs everything indented.

Also add a small docstring to the `networkd` attr in the networking test.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] nix-shell with overlay?

[Profpatsch]

On 17-03-08 01:29am, Nicolas Pierron wrote:
> >> import  {
> >>   overlays: [(self: super: {
> >> myDep = super.myDep.override {
> >>   …
> >> };
> >> myPkg = self.callPackage ./. {};
> 
> nit: super.callPackage, as the super.callPackage *function* already
> aliases self packages.  Otherwise, you would be going twice through
> the fix-point.

Wait, super.callPackage will already have myDep with overrides?
Doesn’t that make the Definition of callPackage questionable?

-- 
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

Re: [Nix-dev] Rust prebuilt package overlay.

[Profpatsch]

On 17-03-08 01:58am, Nicolas Pierron wrote:
> On Tue, Mar 7, 2017 at 1:41 PM, Profpatsch <m...@profpatsch.de> wrote:
> > On 17-03-04 08:34pm, Nicolas Pierron wrote:
> >> The *.toml manifest file is then parsed (yes, in Nix [3]) to extract
> >> [3] 
> >> https://github.com/mozilla/nixpkgs-mozilla/blob/master/lib/parseTOML.nix
> >
> > what have you done
>
> If you want more detail, maybe I should present it at the next NixCon.

Yes, please, in the recreational hacking section. :)

-- 
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

Re: [Nix-dev] nix-shell with overlay?

[Profpatsch]

On 17-03-07 03:57pm, Matthias Beyer wrote:
> Hi,
> 
> is there a way to import an overlay in a default.nix for a nix-shell 
> and use the packages from the overlay in the nix-shell only, without 
> installing the overlay "globally" for my user?
> 
> If yes, how?

Not sure what you mean, how about just adding the overlay to the default.nix?

import  {
  overlays: [(self: super: {
myDep = super.myDep.override {
  …
};
myPkg = self.callPackage ./. {};
  })];
}

nix-build -A myPkg

echo "(import ./.).myPkg" > shell.nix
nix-shell

-- 
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

Re: [Nix-dev] 'nixos-stable' channel?

[Profpatsch]

On 17-03-06 04:03pm, Domen Kožar wrote:
> It's something like 15min of work to parse http://nixos.org/channels/ and
> point to the latest channel if someone needs this.
> 
> Officially this is a very bad idea, since people will want us to support it.

Also ignoring the idea behind stable upgrades,
that breaking changes are almost guaranteed.


-- 
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

Re: [Nix-dev] Rust prebuilt package overlay.

[Profpatsch]

On 17-03-04 08:34pm, Nicolas Pierron wrote:
> The *.toml manifest file is then parsed (yes, in Nix [3]) to extract
> [3] https://github.com/mozilla/nixpkgs-mozilla/blob/master/lib/parseTOML.nix

what have you done

-- 
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

Re: [Nix-dev] libgfortran.so missing

[Profpatsch]

On 17-02-21 11:11pm, rohit yadav wrote:
> Hi,
> 
> I could not find the above mentioned shared object lib in any of the
> nixpkgs. Could please someone let me know which package to install this to
> get lib? gcc or gfortran does not install this

The gfortran attribute only produces a wrapper.
The actual compiler is gfortran.cc; the .so is in gfortran.cc.lib

Hope that helps.

An easy way to find shared objects and the names of
packages they are in is to use find(1) on the store btw:

find /nix/store -iname "*libgfortran.so*"


-- 
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-commits] [NixOS/nixpkgs] 07bf11: garden-of-coloured-lights: init at 1.0.9

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 07bf113bbe79640ad044177751b2da9dc94b70c2
  
https://github.com/NixOS/nixpkgs/commit/07bf113bbe79640ad044177751b2da9dc94b70c2
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-03-06 (Mon, 06 Mar 2017)

  Changed paths:
A pkgs/games/garden-of-coloured-lights/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  garden-of-coloured-lights: init at 1.0.9


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Qt and KDE updates

[Profpatsch]

On 17-02-28 09:19pm, Bjørn Forsman wrote:
> On 28 February 2017 at 21:10, Vladimír Čunát  wrote:
> > On 02/28/2017 12:51 PM, Thomas Tuegel wrote:
> >> Package maintainers should read the updated Qt and KDE documentation in
> >> the Nixpkgs manual (unfortunately this is not updated on nixos.org yet;
> >> you can build the manual yourself or read the source on GitHub [1]).
> >
> > http://nixos.org/nixos/manual/ shows the one for 16.09 on purpose
> > (current stable), so it should not be there yet.
> 
> I guess this is stating the obvious, but we really should have the
> manuals for both stable and unstable available on nixos.org (IMHO).

Better yet, build and expose the manuals of the current system
to the user locally.

Offline all the docs \o/

-- 
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

Re: [Nix-dev] "Consider the Maintainer"

[Profpatsch]

On 17-02-18 10:58pm, Graham Christensen wrote:
> Linux.conf.au had this great talk called "Consider the Maintainer" about
> being a software maintainer, and managing open source projects. I'd
> encourage you all to watch it:
> 
> https://www.youtube.com/watch?v=W2AR1owg0ao

There’s also a talk called “Package Managers all the way down”,
talking about what pms are, system pms and especially
language-specific pms, large numbers of dependencies (npm style)
and projects that may be part of the solution.

And yes, nix is his first proposed solution
and also comes up in the questions afterwards. :)

-- 
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

Re: [Nix-dev] Best Practices on Modularizing Configuration.nix?

[Profpatsch]

On 17-02-27 09:15am, Mark Gardner wrote:
> Now that I am putting NixOS on more and more machines, I would like to
> modularize and share parts of the config to maximize reuse and ensure
> uniformity. 

As far as the non-dev-ops-y parts go
(that is: the nix expression parts),
there’s basically two ways to structure modules:

1. Using `import`
2. Using `imports` from the module system
3. Using option definitions

All have their place, I personally use the first
two for more ephemeral settings and the latter if
I want to share something for use by others.

Example from my current machine config in our vuizvui repo:

I have a folder for my personal machines, with a lib.nix
and pkgs.nix; these are included as attrsets with `import`
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/katara.nix#L4

My config for workstation/server/base is split into various
module files, which get included with `imports`.
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/katara.nix#L9
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/base-workstation.nix#L11

Then finally there’s the Thinkpad-specific setup,
which I have put into a module with an enable option
for others to use.
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/katara.nix#L45
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/modules/hardware/thinkpad.nix
and it’s actually used by our hackerspace’s Thinkpad, too:
https://github.com/openlab-aux/vuizvui/blob/cd4bc6fde00e3da0382a3eb151dbbd0087449377/machines/labnet/labtops.nix#L9

I hope that helps.


-- 
Proudly written in Mutt with Vim on NixOS.
Q: Why is this email longer than five sentences?
A: Sometimes you have to be more verbose. :)
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-commits] [NixOS/nixpkgs] e1656b: git-dit: init at 0.1.0

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: e1656bc46da6c2001cfb992735a7daeb75f00bc0
  
https://github.com/NixOS/nixpkgs/commit/e1656bc46da6c2001cfb992735a7daeb75f00bc0
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-25 (Sat, 25 Feb 2017)

  Changed paths:
M pkgs/applications/version-management/git-and-tools/default.nix
A pkgs/applications/version-management/git-and-tools/git-dit/default.nix

  Log Message:
  ---
  git-dit: init at 0.1.0


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] cabal-install & nix (was: nix-shell pro/con (was: Python 3 as default))

[Profpatsch]

On 17-02-23 07:52pm, Thomas Tuegel wrote:
> Profpatsch <m...@profpatsch.de> writes:
> > On 17-02-23 12:45pm, Thomas Tuegel wrote:
> >> The next version of cabal-install will perform this caching for you
> >> automatically. It uses your shell.nix (if present) and adds GC roots for
> >> the results. Your environment is not garbage collected or updated unless
> >> you clear out the work directory or modify the shell.nix.
> >
> > You mean cabal-install will get support for nix?
> > How does that interact with new-style builds?
> 
> Nix integration only supports the commands [1] where I thought it would
> be useful, which does not include new-build. Adding support for a new
> command wouldn't be difficult; "Nix integration" simply consists of
> cabal calling `exec nix-shell --run "cabal [original arguments...]"'.

Hm, that’s a nice convenience feature, but I’m rather sceptical.
Adding „nix support“ of one kind or another to all domain tooling
will lead to an at least quadratic blowup of duplicated work
and special, probably hardly maintained config options everywhere.

It’s in stack (and it sucks afaik), now it’s in cabal, next in pip …

-- 
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

Re: [Nix-dev] cabal-install & nix (was: nix-shell pro/con (was: Python 3 as default))

[Profpatsch]

On 17-02-23 12:45pm, Thomas Tuegel wrote:
> The next version of cabal-install will perform this caching for you
> automatically. It uses your shell.nix (if present) and adds GC roots for
> the results. Your environment is not garbage collected or updated unless
> you clear out the work directory or modify the shell.nix.

You mean cabal-install will get support for nix?
How does that interact with new-style builds?

-- 
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-commits] [NixOS/nixpkgs] 8e54fc: flpsed: ghostscript patch, fixes, new url

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 8e54fced988e4227c34bfc21417ac41eda4448c6
  
https://github.com/NixOS/nixpkgs/commit/8e54fced988e4227c34bfc21417ac41eda4448c6
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-23 (Thu, 23 Feb 2017)

  Changed paths:
M pkgs/applications/editors/flpsed/default.nix

  Log Message:
  ---
  flpsed: ghostscript patch, fixes, new url

gs was called at runtime, fix the execvp call.
The url changed to its own domain.
A little face-lift for the package code.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 31dac1: mpd: add avahi zeroconf support

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 31dac10c330faf453ba946cbf558c04ca19102b9
  
https://github.com/NixOS/nixpkgs/commit/31dac10c330faf453ba946cbf558c04ca19102b9
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-18 (Sat, 18 Feb 2017)

  Changed paths:
M pkgs/servers/mpd/default.nix

  Log Message:
  ---
  mpd: add avahi zeroconf support


  Commit: 2b0469c48f3211425ed06ae3ee5f257f97d9753c
  
https://github.com/NixOS/nixpkgs/commit/2b0469c48f3211425ed06ae3ee5f257f97d9753c
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-18 (Sat, 18 Feb 2017)

  Changed paths:
M nixos/modules/services/audio/mpd.nix

  Log Message:
  ---
  modules/mpd: factor out name & mention man 5 mpd.conf


Compare: https://github.com/NixOS/nixpkgs/compare/313ccd5be3bf...2b0469c48f32___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 9debda: networking.bonds: add support for arbitrary driver...

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9debdaf512bc510f7f5d5450c4902e7d1f713274
  
https://github.com/NixOS/nixpkgs/commit/9debdaf512bc510f7f5d5450c4902e7d1f713274
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-16 (Thu, 16 Feb 2017)

  Changed paths:
M nixos/modules/tasks/network-interfaces-scripted.nix
M nixos/modules/tasks/network-interfaces.nix
M nixos/tests/networking.nix

  Log Message:
  ---
  networking.bonds: add support for arbitrary driverOptions

Until now the four attributes available very selectively provided a small
subset, while copying upstream documentation.

We make driver options an arbitrary key-value set and point to kernel
documentation, which is always up-to-date. This way every option can be set.
The four already existing options are deprecated with a warning.


  Commit: bb797c1390971753f17f33882cfd477bc0f6d186
  
https://github.com/NixOS/nixpkgs/commit/bb797c1390971753f17f33882cfd477bc0f6d186
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-16 (Thu, 16 Feb 2017)

  Changed paths:
M nixos/modules/system/boot/networkd.nix
M nixos/modules/tasks/network-interfaces-systemd.nix

  Log Message:
  ---
  networking.networkd: adjust autmatic mapping of bonds

Since the bonds interface changed to a lot more possible values we create a
mapping of kernel bond attribute names and values to networkd attributes.
Those match for the most part, but have to transformed slightly.

There is also an assert that unknown options won’t slip through silently.


Compare: https://github.com/NixOS/nixpkgs/compare/03024b39b7d4...bb797c139097___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Explicitly selecting sources for "src" in stdenv.mkDerivation?

[Profpatsch]

On 17-02-16 01:28pm, Freddy Rietdijk wrote:
> > src = [ ./subproject-A/schema.sql ./subproject-A/lib ];
> 
> Each of the files you mentioned here will be stored in a separate store
> path. You could write a simple function that takes a list of derivations
> and copies the contents of those derivations in a new output.

Also maybe take a look at the `filterSource` builtin.
There’s also some wrappers for common setups in lib/sources.nix

-- 
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

Re: [Nix-dev] nix-shell pro/con (was: Python 3 as default)

[Profpatsch]

On 17-02-15 09:10pm, Ricardo M. Correia wrote:
> Personally, I try to avoid using "nix-shell" as much as possible because I
> want "nixos-rebuild switch" to atomically install (and upgrade) all the
> software that I usually need, including development packages.
> 
> With nix-shell, I risk having the packages I need become outdated (without
> me noticing) and/or become garbage collected (which I do every day
> automatically) and unavailable if I lose Internet access (e.g. because I'm
> traveling).

I think you are confusing nix-env and nix-shell; nix-shell can’t have
“outdated” packages, it will use what you specify.

packages being not cached is a largely orthogonal problem;
for example it would be quite easy to create a script that fetches
the nix-shell deps for all your projects and creates a folder with
gc-roots.

For long-running projects I use `git worktree` to have a stable
checkout. If you want to get fancy you could set up a hydra
if you want to follow e.g. stable with your own patches applied.

-- 
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-commits] [NixOS/nixpkgs] 21cdf3: pythonPackages: use a more direct mirror (#22833)

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 21cdf340dbdc6ba5dca4e9dc1532b17d251e77ba
  
https://github.com/NixOS/nixpkgs/commit/21cdf340dbdc6ba5dca4e9dc1532b17d251e77ba
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-15 (Wed, 15 Feb 2017)

  Changed paths:
M pkgs/build-support/fetchurl/mirrors.nix

  Log Message:
  ---
  pythonPackages: use a more direct mirror (#22833)

The pypi.io domain is redirected two (!) times and lands on the URL added by
this commit.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 91d026: modules/filesystems: disallow non-empty fstab fiel...

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 91d0260feba50b25b13d1e0dd2705039f75e09a2
  
https://github.com/NixOS/nixpkgs/commit/91d0260feba50b25b13d1e0dd2705039f75e09a2
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-15 (Wed, 15 Feb 2017)

  Changed paths:
M nixos/modules/tasks/filesystems.nix

  Log Message:
  ---
  modules/filesystems: disallow non-empty fstab fields (#22803)

It was possible to pass empty strings / strings with only separator characters;
this lead to broken fstab formatting.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 7ee777: picard: 1.32. -> 1.4

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 7ee777d784de06a088c5ec933bfb2383c7001d1f
  
https://github.com/NixOS/nixpkgs/commit/7ee777d784de06a088c5ec933bfb2383c7001d1f
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-15 (Wed, 15 Feb 2017)

  Changed paths:
M pkgs/applications/audio/picard/default.nix

  Log Message:
  ---
  picard: 1.32. -> 1.4


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Python 3 as default

[Profpatsch]

On 17-02-14 01:18pm, Peter Simons wrote:
> I hardly ever use nix-shell and I don't want to, to
> be honest

Completely off-discussion: Why is that?
Convenience? nix-shell does too many strange things?

Personally I use nix-shell for nearly everything I do
nowadays because it’s so convenient.
Even a buildFHSUserEnv is quickly set up for strange software.

-- 
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

Re: [Nix-dev] Python 3 as default

[Profpatsch]

On 17-02-13 10:08am, Freddy Rietdijk wrote:
> In any case, I would like to merge this as soon as possible. Any objections?

+1 go for it; Good work!

progress is breakage is progress \o/

-- 
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-commits] [NixOS/nixpkgs] 5b2a71: droopy: init at 20160830 (#22499)

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 5b2a71fa250926010e6da0a6c6325dc1270770c1
  
https://github.com/NixOS/nixpkgs/commit/5b2a71fa250926010e6da0a6c6325dc1270770c1
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-11 (Sat, 11 Feb 2017)

  Changed paths:
A pkgs/applications/networking/droopy/default.nix
M pkgs/top-level/all-packages.nix

  Log Message:
  ---
  droopy: init at 20160830 (#22499)


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] ed8a0d: modules/searx: add package option (#22636)

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: ed8a0d8e5e1b1de29db72373471b201b69865812
  
https://github.com/NixOS/nixpkgs/commit/ed8a0d8e5e1b1de29db72373471b201b69865812
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2017-02-10 (Fri, 10 Feb 2017)

  Changed paths:
M nixos/modules/services/networking/searx.nix

  Log Message:
  ---
  modules/searx: add package option (#22636)

The user should be able to specify a patched version of searx.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] nix-bundle: Bundle Nix derivations to run anywhere

[Profpatsch]

On 17-02-07 11:48am, Tomasz Czyż wrote:
> I would vote for mirroring this tool in nixos github namespace (or even
> trying to make this project official one) as it can have big impact of
> propagating/implementing nix ideas into environments where it's not
> straight forward to use it.
> 
> What do you think people?

+1


-- 
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] cache.nixos.org is down

[Profpatsch]

It’s kind of flaky, so `curl https://cache.nixos.org`
sometimes cannot resolve the host and sometimes outputs 404.

-- 
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

Re: [Nix-dev] Arch is dropping i686. Should we?

[Profpatsch]

On 17-01-26 08:37am, Graham Christensen wrote:
> One person on IRC said they think they may have used it once. Does
> anyone on this list use NixOS on i686? anyone on this list know anyone
> using NixOS on i686?

I’m using it for one old machine running the audio server
of our hackerspace.

-- 
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

Re: [Nix-dev] Is it possible to limit nix access to sudoers and/or a group?

[Profpatsch]

On 17-01-20 10:59am, Danylo Hlynskyi wrote:
> Nix design doesn't support quotas on filled store per-user, and let's not
> forget #8.

https://github.com/NixOS/nixpkgs/pull/8 ?

That looks unrelated.

-- 
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] Add @goetzst to maintainers

[Profpatsch]

I suggest adding https://github.com/goetzst to nixpkgs.
He is very thoroughly managing youtube-dl and probably
some other packages.
-- 
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

Re: [Nix-dev] Trying to install the SailfishOS SDK

[Profpatsch]

On 17-01-19 09:13pm, Christoph-Simon Senjak wrote:
> I get the error message
> 
> Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions:
> Assertion `needed != NULL' failed!
> 
> Any ideas what I could do about that?

I am not sure, but have you tried a search, like:
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions

Normally every possible linker error has already bitten
someone else in the past.

-- 
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

Re: [Nix-dev] Typing nix − funding campaign

[Profpatsch]

On 17-01-12 07:31pm, Théophane Hufschmitt wrote:
> I'd want to support exactly the same syntax as nix does. That would
> mean (depending of the position of the nix core-dev team about this)
> either that the nix syntax would be extended to support type
> annotations, either that those would be included in comments.

If you want to write a nix parser, you can take a look at 
https://hackage.haskell.org/package/hnix

Also, Gabriel took a quick shot at one, but it’s unfinished:
https://github.com/Gabriel439/nixfmt

Hope it works for you, writing parsers is tricky. Especially the
string splicing in nixexprs.

-- 
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.


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Call For Maintainers - Fractalide BETA release

[Profpatsch]

On 17-01-12 09:16pm, stewart mackenzie wrote:
> Reproducible functions adds a new vertical design space to Nix/NixOS,
> it's pretty huge in my books, given that monolith apps can be combined
> in only a certain amount of ways. Next came the reproducible
> libraries, which can be combined into even more ways. Now this new
> feature introduces a whole new level of mix-and-matchability.

I didn’t want to appear condescending, I just saw a big (very big)
wall of tl;dr text and a quick overview and why this is interesting
to Nix(OS) developers would be very helpful.

Can you provide a pitch in two sentences?
(that will be important to tell people about your probably very
interesting idea in general!)

-- 
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

Re: [Nix-dev] Typing nix − funding campaign

[Profpatsch]

On 17-01-12 02:13pm, Théophane Hufschmitt wrote:
> type system for nix

I’m excited.

> Numtide offered to fund a part of the internship, but we still need
> some help for me to be able to start it.

If GsoC can be made to work, maybe the $5000 (or something like that)
can be added? Not sure if that is allowed from the GsoC rules though.


-- 
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.


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Call For Maintainers - Fractalide BETA release

[Profpatsch]

On 17-01-11 11:34pm, stewart mackenzie wrote:
> Greetings all,

Not sure what this has to do with nix-dev?

-- 
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

Re: [Nix-dev] Google Summer of Code 2017

[Profpatsch]

On 17-01-04 09:42pm, Vladimír Čunát wrote:
> On 01/04/2017 08:51 PM, Peter Simons wrote:
> > Another very important topic that needs to be addressed in Nix / Hydra
> > is the question of how to deal with code that wants to import build
> > products into the ongoing evaluation. [...]
> 
> That feels rather vague topic ATM.  My experience is that this kind of
> "figure it out how to..." tasks isn't very suitable for similar "project
> proposals" like for GSoC.  Still, if we could converge on some more
> concrete plan beforehand, maybe the actual implementation would make a
> good topic...

Sounds more like a task for a master’s thesis (or adventurous
bachelor’s thesis) to 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-commits] [NixOS/nixpkgs] 52c34f: liquibase: improve external jar integration (#2081...

[Profpatsch]

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 52c34f626ca54b8d664dbba925bd5cfc959f9dc7
  
https://github.com/NixOS/nixpkgs/commit/52c34f626ca54b8d664dbba925bd5cfc959f9dc7
  Author: Profpatsch <m...@profpatsch.de>
  Date:   2016-12-16 (Fri, 16 Dec 2016)

  Changed paths:
M pkgs/development/tools/database/liquibase/default.nix

  Log Message:
  ---
  liquibase: improve external jar integration (#20818)

This replaces the upstream wrapper script with one tailored for nixpkgs.
We gain the ability to selectively enable/disable jdbc backends.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Usability: Nixpkg > NixOS

[Profpatsch]

On 16-12-15 11:48pm, Judson Lester wrote:
> First, how derivations become software. I *think* nix-env (or nix-shell, or
> nix-repl) takes the derivation, finds the build script, establishes
> environment variables and runs the script, but I don't know that I've ever
> seen that in print anywhere.

nix-store --realise

> More nuanced, I've never quite been sure where
> the appropriate dividing line is between derivation and build script

The whole definition is in the nix manual in the derivation section.
For specific details you would probably need to read the nix source.

> Second, how do builds get linked into the system? I've seen it happen, and
> again I have suspicions that it has to do with the outputs attribute of the
> derivation, but I remain in the spooky darkness about particulars.

System profiles are just a derivation that is basically a link farm.
In their /bin they have a bash script that performs the actual switch.
It basically bootstraps itself.


-- 
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

Re: [Nix-dev] Usability: Nixpkg > NixOS

[Profpatsch]

On 16-12-15 02:21pm, Colin Putney wrote:
> Perhaps if we promote the language more, people will get over that hurdle
> early and then be pleasantly surprised when they see what's possible with
> it.

see also: https://nixcloud.io/tour/


-- 
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] PSA We’ve breached 1400 issues

[Profpatsch]

It’s very easy to make them go down:

1) Go to this page (issues, least recently updated first)
https://github.com/NixOS/nixpkgs/issues?utf8=%E2%9C%93=is%3Aopen%20sort%3Aupdated-asc%20
2) Click on the first
3) Skim over the contents
4) Write: "(triage) Any updates?" or similar, maybe more fitting
5) After two weeks close the issue
 / ask a maintainer to close it for you
Often the issue will have solved itself.

Go forth and close some issues!

-- 
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