[Nix-dev] Hydra seems to be down

I’m not sure if this is the best place, but: hydra.nixos.org is not responding to requests. http://isitup.org/hydra.nixos.org This service confirms that it’s not just my local network. It works very seldomly, sometimes after 15 minutes, so it looks more like an overload problem. -- Proudly writ

[Nix-dev] Literal “magic” strings in nixpkgs

I noticed there is a trend to use magic strings in some places of nixpkgs, e.g. in https://nixos.org/nixos/manual/ch-options.html#opt-security.pki.certificateFiles where the example is: [ "${pkgs.cacert}/etc/ca-bundle.crt" ] I find that alarming, because in exactly that case it silently broke whe

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-19 02:56am, Roger Qiu wrote: > Can the manual be made as a gitbook with the chapters fleshed out better > and made more user friendly? One part of the manual can be very fact > based, another part can be story based. Kind of like the difference between > documentation vs api documentation

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-19 05:17pm, Cillian de Róiste wrote: > 2015-11-19 16:57 GMT+01:00 Profpatsch : > > On 15-11-19 02:56am, Roger Qiu wrote: > > May I humbly suggest http://stevelosh.com/blog/2013/09/teach-dont-tell/ as > > a general documentation writing template? > > I'm a

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-23 08:03pm, Jan Malakhovski wrote: > That is, I'd like > > * All the docs to be available and discoverable locally. > /run/current-system/sw/share/doc FTW. (easy to do) Yes, please. > * To have a thing that indexes all the man, info and haddock pages for > full text search using e.g

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

On 15-11-24 09:14pm, zimbatm wrote: > Please no XML as the source, it adds way too much emphasis on the structure > instead of the content. > > Asciidoc is pretty good. It can be configured quite close to markdown >

Re: [Nix-dev] Meetup in Munich today

On 15-11-25 03:51pm, Franz Pletz wrote: > Don't worry, no advertising for our company will take place. We're not > yet using NixOS here but we're actively trying to infect all our > co-workers and the management. Having an active local community is one > of the best first steps in our opinion. ;)

Re: [Nix-dev] Fundraiser?

On 15-12-07 04:36pm, Tomasz Czyż wrote: > https://www.bountysource.com/search?query=nixos - maybe this is good > enough, no? Just needs a little more advertisement :-) My problem with Bountysource is that most bounties are a flipping joke compared to what someone would earn in even badly paid jobs

Re: [Nix-dev] Set up a Sufficiently Powerful Build Farm

On 15-12-22 10:27am, Christian Theune wrote: > I could put one or more mac minis in our office on a reasonable big pipe > (100mbit fibre up/down). Question is whether we could fund them somehow. > Would a single additional machine help or do we need multiple? (For > anchoring: the app store pric

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

On 16-01-04 12:34am, em...@vfemail.net wrote: > If someone is interested in a pure Rust implementation, then a prerequsite > would be to > come up with a rigorous definition of the language and all of the builtins, > and then > identifying the unix specific builitins and derivation behavior. I

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

Full ack for flattening all-packages.nix. I didn’t even know there where sections until a few days ago, the file is simply too large. Let’s just sort the top level by alphabet. On 16-01-08 01:10am, Luca Bruno wrote: > So I propose to still have directories, but chosen by maintainers. For > example

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

On 16-01-08 08:53am, Daniel Peebles wrote: > and that > all-packages.nix should be abolished (use builtins.readDir by default and a > manual overrides file where necessary) Strong -1 on this one. #1: Explicit is better than implicit Things will get very ugly. -- Proudly written in Mutt with V

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

On 16-01-08 10:16pm, Tomasz Czyż wrote: > 2016-01-08 14:58 GMT+00:00 Vladimír Čunát : > > The largest problem I see for categorization is ambiguity (mentioned > > already). The "categories" will always overlap nontrivially, so we would > > better track such information in a different way than direc

[Nix-dev] Regarding the Wiki

We have basically decided to shut it down soon (™), right? Just now I tried to set up my printer again. For that I first looked at docs and the source, which didn’t provide any helpful info, and then I found the article on generating the correct Cups files here: https://nixos.org/wiki/Printers If

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

On 16-01-09 10:56am, Jonathan Glines wrote: > 2016/01/09 午前10:36 "Profpatsch" : > > > > On 16-01-08 08:53am, Daniel Peebles wrote: > > > and that > > > all-packages.nix should be abolished (use builtins.readDir by default > and a > > > manu

[Nix-dev] Notes and ideas about the Nix-UI proposal

Eelco wrote a first proposal about the new nix CLI tool https://gist.github.com/edolstra/efcadfd240c2d8906348 I thought about it and wrote down a few ideas and proposals where I think that can be improved: https://gist.github.com/Profpatsch/d5c8e1ccd68baab0e3f0 In particular I think I have found

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

On 16-01-20 06:24pm, Owen Lynch wrote: > Hello, > > I'm wondering if there is a standard/recommended way to put > /etc/nixos/configuration.nix under version control. It would make managing > lots of virtual machines a lot easier, because I could have a script that > updated to the latest configura

Re: [Nix-dev] Redesign of documentation

On 16-02-15 06:57pm, Freddy Rietdijk wrote: > Furthermore, I can imagine a third > part with How To's could be added to the Nix user guide. These are commonly called “Cookbook” and in my experience they are an invaluable source of practical information. We kind of have something similar in the cu

Re: [Nix-dev] Wiki is dead

On 16-02-14 09:15pm, zimbatm wrote: > But before I invest more time, do you think it's a path worth pursuing ? > Also what would be required for this to be considered "ready" ? Wow, that’s great! What are your thoughts on converting it to a nixos (and nix) cookbook, akin to the Python Cookbook (h

[Nix-dev] codetriage.com

I just created a Repo page for nixpkgs at codetriage.com. It is a simple site that sends you 1 open issue each day once you sign up with your Github account. Maybe a few people want to join me. -- Proudly written in Mutt with Vim on NixOS. Q: Why is this email five sentences or less? A: http://

Re: [Nix-dev] Installing CA certificates

On 16-02-18 01:53pm, Adam Russell wrote: > Hello Nix-Dev, > > I'm trying to understand how to install CA certificates in NixOS. Different question, related topic: I tried adding CA-Cert by default a while ago and had the impression it worked for a while and then suddenly stopped working (at leas

Re: [Nix-dev] codetriage.com

On 16-02-17 08:18pm, Rok Garbas wrote: > I would suggest closing tickets that you think are not crucial or > reporter does not provide code that we can include. Ofcourse be nice > in comment and ask reported to reopen if they think you are wrong to > do this. > > What you say, could this work and

Re: [Nix-dev] Fwd: Wiki is dead

On 16-02-20 03:11pm, Anthony Cowley wrote: > The point being that once a wiki item gets a handful of positive votes, it > gets turned into an Issue on the manual for someone with a better > understanding of how things are put together to find it a home. At that > point, the wiki item could have a l

Re: [Nix-dev] Fwd: Wiki is dead

> On Tue, 23 Feb 2016 at 21:29 Vladimír Čunát wrote: > > My personal opinion is that this is mostly an excuse. It's a XML subset > > and everyone should know at least a bit of (X)HTML or similar stuff. > > Note that for almost all docs we use ~10 types of tags and the format is > > by itself human

Re: [Nix-dev] Open source team messaging: mattermost

On 16-03-01 11:46pm, Teo Klestrup Röijezon wrote: > Plain IRC sucks. It’s true, but it f* works. Especially for developers, devs who can’t configure an IRC client? Are those people devs? But I know the pain. Hm, we even use IRC as main communication tool in our Hackerspace, and so far even non

Re: [Nix-dev] NixON initiative

On 16-02-28 04:44pm, zimbatm wrote: > So something like that ? https://github.com/NixOS/nixpkgs/pull/13552 > And then we would convert all of our tooling to output JSON ? As long as nixexprs embedded in the JSON are *not* evaluated in any way, we are fine. Think of { "hello" = "{ foo = (abort

Re: [Nix-dev] new tool: nixos-typecheck

On 16-02-29 03:16am, Hash Domains wrote: > What do you think? Tried to test it on my local nixpkgs, but can’t get it working. nixpkgs> nixos-typecheck printUnspecified ./nixos error: attribute ‘typechecker’ in selection path ‘typechecker.printUnspecified’ not found Happens also with --help, so

Re: [Nix-dev] Tool: Better code search on NixOS/*

On 16-03-04 08:25am, Vladimír Čunát wrote: > 2. > We have ctags wrapped with simple regexp that indexes simple 'foo =' > bindings. That has the advantage of integrating smoothly with many editors. Uh, that would be nice. Do you have a link? Right now I manually do the `foobar.=` search with ag

Re: [Nix-dev] new tool: nixos-typecheck

On 16-03-04 01:51pm, Thomas Strobel wrote: > Does the following command work: "nixos-typecheck printUnspecified -I > nixpkgs=/path/to/nixpkgs/from/PR/13607" ? It does indeed. But why can’t I directly give it the path to a module? -- Proudly written in Mutt with Vim on NixOS. Q: Why is this ema

Re: [Nix-dev] Open source team messaging: mattermost

On 16-03-08 06:30am, Wout Mertens wrote: > With IRC, you have to open your client, fire off your question a few times > and hope that someone will know the answer eventually. I can't have IRC > open at work all day. You haven't heard of bouncers? ZNC for example. If as a developer you run an IRC c

Re: [Nix-dev] Difference between Pkgs, Super and Self in this Snippet

On 16-04-13 06:56pm, Nicolas Pierron wrote: > On Mon, Apr 11, 2016 at 7:34 AM, Roger Qiu wrote: > > ``` > > { pkgs }: { # pkgs is the fully configured packages, after overrides > >packageOverrides = super: let self = super.pkgs; in rec { # super is > > without overrides, self is with > >

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

On 16-04-09 04:10pm, Anderson Torres wrote: > I prefer to start a documentation project, like the FreeBSD > Handbook[1]. It could contain some in-project documentation for every > module too. I proposed a Cookbook a while ago, akin to the Puppet one http://www.puppetcookbook.com/ We could write t

Re: [Nix-dev] Difference between Pkgs, Super and Self in this Snippet

and also their override mechanism which is very similar. e.g. https://github.com/openlab-aux/vuizvui/blob/master/machines/profpatsch/pkgs.nix#L15 -- 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 y

Re: [Nix-dev] Upcoming PyPi URL Scheme Change

On 16-04-20 11:41am, Graham Christensen wrote: > I recently got word that PyPi is changing their URL scheme. > > Old example: > https://pypi.python.org/packages/source/a/ansible/ansible-1.8.2.tar.gz#md5=c2ac0e5a4c092dfa84c7e9e51cd45095 > > New example: > https://pypi.python.org/packages/62/18/91f

Re: [Nix-dev] break purity

On 16-04-22 06:33pm, Oliver Charles wrote: > It's certainly possible, because I just did it with Haskell ;) > > https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab Why do you need to put the atime two hours in the past? Does cabal recompilation check for it in order to find out what

Re: [Nix-dev] Monitoring by default

On 16-04-22 02:08pm, Svein Ove Aas wrote: > - And I don't suppose I can deny being at Google, no, but this isn't a > Google project; I've just ended up using NixOS *everywhere* in my personal > life, so now I want monitoring. ;-) That’s what they always say right before they make a 10 person team

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

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

[Nix-dev] Add @goetzst to maintainers

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

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

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

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

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

[Nix-dev] cache.nixos.org is down

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

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

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

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: ed8a0d8e5e1b1de29db72373471b201b69865812 https://github.com/NixOS/nixpkgs/commit/ed8a0d8e5e1b1de29db72373471b201b69865812 Author: Profpatsch Date: 2017-02-10 (Fri, 10 Feb 2017) Changed paths: M

[Nix-commits] [NixOS/nixpkgs] 5b2a71: droopy: init at 20160830 (#22499)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 5b2a71fa250926010e6da0a6c6325dc1270770c1 https://github.com/NixOS/nixpkgs/commit/5b2a71fa250926010e6da0a6c6325dc1270770c1 Author: Profpatsch Date: 2017-02-11 (Sat, 11 Feb 2017) Changed paths: A

Re: [Nix-dev] Python 3 as default

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

Re: [Nix-dev] Python 3 as default

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

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 7ee777d784de06a088c5ec933bfb2383c7001d1f https://github.com/NixOS/nixpkgs/commit/7ee777d784de06a088c5ec933bfb2383c7001d1f Author: Profpatsch Date: 2017-02-15 (Wed, 15 Feb 2017) Changed paths: M

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 91d0260feba50b25b13d1e0dd2705039f75e09a2 https://github.com/NixOS/nixpkgs/commit/91d0260feba50b25b13d1e0dd2705039f75e09a2 Author: Profpatsch Date: 2017-02-15 (Wed, 15 Feb 2017) Changed paths: M

[Nix-commits] [NixOS/nixpkgs] 21cdf3: pythonPackages: use a more direct mirror (#22833)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 21cdf340dbdc6ba5dca4e9dc1532b17d251e77ba https://github.com/NixOS/nixpkgs/commit/21cdf340dbdc6ba5dca4e9dc1532b17d251e77ba Author: Profpatsch Date: 2017-02-15 (Wed, 15 Feb 2017) Changed paths: M

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

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 th

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

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 derivati

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 9debdaf512bc510f7f5d5450c4902e7d1f713274 https://github.com/NixOS/nixpkgs/commit/9debdaf512bc510f7f5d5450c4902e7d1f713274 Author: Profpatsch Date: 2017-02-16 (Thu, 16 Feb 2017) Changed paths: M

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 31dac10c330faf453ba946cbf558c04ca19102b9 https://github.com/NixOS/nixpkgs/commit/31dac10c330faf453ba946cbf558c04ca19102b9 Author: Profpatsch Date: 2017-02-18 (Sat, 18 Feb 2017) Changed paths: M

[Nix-commits] [NixOS/nixpkgs] 8e54fc: flpsed: ghostscript patch, fixes, new url

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 8e54fced988e4227c34bfc21417ac41eda4448c6 https://github.com/NixOS/nixpkgs/commit/8e54fced988e4227c34bfc21417ac41eda4448c6 Author: Profpatsch Date: 2017-02-23 (Thu, 23 Feb 2017) Changed paths: M

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

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

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

On 17-02-23 07:52pm, Thomas Tuegel wrote: > Profpatsch 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 > >&

[Nix-commits] [NixOS/nixpkgs] e1656b: git-dit: init at 0.1.0

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: e1656bc46da6c2001cfb992735a7daeb75f00bc0 https://github.com/NixOS/nixpkgs/commit/e1656bc46da6c2001cfb992735a7daeb75f00bc0 Author: Profpatsch Date: 2017-02-25 (Sat, 25 Feb 2017) Changed paths: M

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

ne 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/serve

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

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 call

Re: [Nix-dev] Qt and KDE updates

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;

[Nix-commits] [NixOS/nixpkgs] 07bf11: garden-of-coloured-lights: init at 1.0.9

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 07bf113bbe79640ad044177751b2da9dc94b70c2 https://github.com/NixOS/nixpkgs/commit/07bf113bbe79640ad044177751b2da9dc94b70c2 Author: Profpatsch Date: 2017-03-06 (Mon, 06 Mar 2017) Changed paths: A

Re: [Nix-dev] libgfortran.so missing

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

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

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 o

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

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,

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

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 j

[Nix-commits] [NixOS/nixpkgs] feab71: lilyterm-git: init at 2017-01-06

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: feab711f84f32ff92978b971585026ed247e3a98 https://github.com/NixOS/nixpkgs/commit/feab711f84f32ff92978b971585026ed247e3a98 Author: Profpatsch Date: 2017-03-07 (Tue, 07 Mar 2017) Changed paths: M

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

On 17-03-08 01:58am, Nicolas Pierron wrote: > On Tue, Mar 7, 2017 at 1:41 PM, Profpatsch 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/moz

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

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.

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 22c265182f9e0d543de0fe46a809180ff2021b85 https://github.com/NixOS/nixpkgs/commit/22c265182f9e0d543de0fe46a809180ff2021b85 Author: Profpatsch Date: 2017-03-08 (Wed, 08 Mar 2017) Changed paths: M

[Nix-commits] [NixOS/nixpkgs] 9dc3f7: networking/bonds: fix examples

Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 9dc3f75b0b2136e132743de3d4b46d14d15f031a https://github.com/NixOS/nixpkgs/commit/9dc3f75b0b2136e132743de3d4b46d14d15f031a Author: Profpatsch Date: 2017-03-08 (Wed, 08 Mar 2017) Changed paths

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

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 g

Re: [Nix-dev] fetchgit

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 ~/l

Re: [Nix-dev] fetchgit

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?

Re: [Nix-dev] Move NodeJS to separate overlay repository?

On 17-03-11 09:46pm, zimbatm wrote: > And finally, I don't want > nixpkgs to be much larger and slow down my `nix-channel --update` because > it's downloading all the haskell, ruby, python, ... library descriptions. > […] Right now it’s a ~10Mb download (tar.xz); See bottom of the mail for full ou

Re: [Nix-dev] fetchgit

I’m not sure, it’s probably just a simple calling error. Can you try with a trivial example? On 17-03-10 09:52am, Sébastien Petitdemange wrote: > +, fetchSubmodules ? true, submodulesList ? "" I’m pretty sure submodulesList should be a list ([]). -- Proudly written in Mutt with Vim on NixOS. Q:

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

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 "*librar

[Nix-commits] [NixOS/nixpkgs] 6da60b: modules/mlmmj: fix a typo in listaddress folder

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 6da60bb10142ba2e63309da048044026f7158d0a https://github.com/NixOS/nixpkgs/commit/6da60bb10142ba2e63309da048044026f7158d0a Author: Profpatsch Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M

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

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

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

On 17-03-17 06:04pm, Volth wrote: > "nix-shell" would be a super option here if it could handle > "installPhase" (this seems easy to fix) and .nix files less trivial > than "hello.nix" (this seems not easy to fix; for example "nix-shell > '' -A linux_4_4" has no "configurePhase", and there are > si

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

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; } Ca

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

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

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

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 ho

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

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

[Nix-dev] Nix release frequency (was: Re: RFC for RFCs)

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

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

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 writ

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

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.

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

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

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

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 d

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

On 17-03-26 09:02am, Luke Clifton wrote: > On 26 Mar. 2017 3:17 am, "Tikhon Jelvis" wrote: > Building statically linked Haskell binaries with Nix has been on my todo > list for a while now. Any hints? It’s not that hard, just look at generic-builder.nix and overwrite everything to use static link

Re: [Nix-dev] garbage-collection of the last 'n' generations

On 17-03-30 02:42pm, Azul wrote: > Hi there, > > I would like to cleanup my oldest 'n' nix generations. > > nix-collect-garbage seems to only provide me with a older than 'n' days > option. > > Any quick hacks to clean everything but keep my recent 'n' generations ? Remove all system links fr

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

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 possibili

[Nix-commits] [NixOS/nixpkgs] a1e617: modules/searx: fix configFile type

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a1e6176cbf3b38cf2ecc8f1543d6c562f509a144 https://github.com/NixOS/nixpkgs/commit/a1e6176cbf3b38cf2ecc8f1543d6c562f509a144 Author: Profpatsch Date: 2017-04-04 (Tue, 04 Apr 2017) Changed paths: M

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

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

[Nix-commits] [NixOS/nixpkgs] 6b5e5d: rss2email: init at 3.9

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 6b5e5de0ef2a040cab9af7388487b16030b877db https://github.com/NixOS/nixpkgs/commit/6b5e5de0ef2a040cab9af7388487b16030b877db Author: Profpatsch Date: 2017-04-05 (Wed, 05 Apr 2017) Changed paths: A

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

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 r

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

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

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 9b7b950832e6ae97c301e8328b797e8b39efb545 https://github.com/NixOS/nixpkgs/commit/9b7b950832e6ae97c301e8328b797e8b39efb545 Author: Profpatsch Date: 2017-04-12 (Wed, 12 Apr 2017) Changed paths: M

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

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 048114eb4f79f3e125dadee106b454e3d72ccdfc https://github.com/NixOS/nixpkgs/commit/048114eb4f79f3e125dadee106b454e3d72ccdfc Author: Profpatsch Date: 2017-04-12 (Wed, 12 Apr 2017) Changed paths: A

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

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 mos

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

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 lengt

  1   2   3   >