[Nix-commits] [NixOS/nixpkgs] 2f0cc0: unclutter-xfixes service: init
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 2f0cc0d3f055d64ca3f4c8664c12e8f02a833d0d https://github.com/NixOS/nixpkgs/commit/2f0cc0d3f055d64ca3f4c8664c12e8f02a833d0d Author: Erik Rybakken <erik.rybak...@math.ntnu.no> Date: 2016-11-29 (Tue, 29 Nov 2016) Changed paths: M nixos/modules/module-list.nix A nixos/modules/services/x11/unclutter-xfixes.nix Log Message: --- unclutter-xfixes service: init Closes #18398 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 897a1b: neomutt: 20160910 -> 20161104 (#20221)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 897a1ba8ff666b51e30e299cf67a57bcf2efb30a https://github.com/NixOS/nixpkgs/commit/897a1ba8ff666b51e30e299cf67a57bcf2efb30a Author: Erik Rybakken <erik.rybak...@math.ntnu.no> Date: 2016-11-07 (Mon, 07 Nov 2016) Changed paths: M pkgs/applications/networking/mailreaders/neomutt/default.nix Log Message: --- neomutt: 20160910 -> 20161104 (#20221) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] a65e1c: neomutt: 20160827 -> 20160910 (#18485)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: a65e1c560c8f51ae79424d37bd858d2762842087 https://github.com/NixOS/nixpkgs/commit/a65e1c560c8f51ae79424d37bd858d2762842087 Author: Erik Rybakken <erik.rybak...@math.ntnu.no> Date: 2016-09-13 (Tue, 13 Sep 2016) Changed paths: M pkgs/applications/networking/mailreaders/neomutt/default.nix Log Message: --- neomutt: 20160827 -> 20160910 (#18485) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 37aff9: ripser: init at 1.0 (#17481)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 37aff96daf96ff84af9ab3a5a1b4a7f6f0144933 https://github.com/NixOS/nixpkgs/commit/37aff96daf96ff84af9ab3a5a1b4a7f6f0144933 Author: Erik Rybakken <erik.rybak...@math.ntnu.no> Date: 2016-08-04 (Thu, 04 Aug 2016) Changed paths: A pkgs/applications/science/math/ripser/default.nix M pkgs/top-level/all-packages.nix Log Message: --- ripser: init at 1.0 (#17481) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] How to get correct length of a string containing non-ascii characters
To anyone interested in this discussion, you may want to follow the issue here: https://github.com/NixOS/nix/issues/770 There I wrote the reason I want this functionality. The main reason is that I want to do as much as possible in Nix, instead of pushing stuff to a building script. Best, Erik On 2016-01-11 23:29, Erik Rybakken wrote: > Hi, > > In nix, when finding the length of a string containing non-ascii characters, > the number of bytes in the representation is returned, instead of the actual > number of characters: > > > nix-repl> builtins.stringLength "å" > > 2 > > Is there any way to get the number of characters instead, or does this > require changes in the core language? > > Best Regards, > Erik Rybakken > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] How to get correct length of a string containing non-ascii characters
Hi, In nix, when finding the length of a string containing non-ascii characters, the number of bytes in the representation is returned, instead of the actual number of characters: > nix-repl> builtins.stringLength "å" > 2 Is there any way to get the number of characters instead, or does this require changes in the core language? Best Regards, Erik Rybakken ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Ideas for a NixOS-related bachelors thesis?
Yes, there is still the trust issue, but one only has to trust the provider of the hashes, not the ones providing the actual files in the IPFS network. Also,if the build is deterministic (another feature mentioned on the GSOC 2015 ideas list), anyone can verify if the hash is valid. One aspect of using IPFS, is that in addition to the nix store, one also have the IPFS store. These two stores have a similar functionality. How will we avoid duplication? Should we just use one store for both nix and IPFS? Best regards, Erik Rybakken On 2015-10-29 12:22, Matthias Beyer wrote: > This sounds also really interesting. > > As far as I can tell, IPFS wouldn't protect me against malformed > packages, so there is still the trust issue. > > Anyways, binary cache on a per-user basis (where I only have to trust > myself) would be a nice thing for the first step. > > Will note that as an idea! > > On 29-10-2015 11:16:51, Domen Kožar wrote: > > I'd go for: https://ipfs.io/ for binary substitues > > > > On Thu, Oct 29, 2015 at 11:15 AM, Joel Moberg <joel.mob...@gmail.com> wrote: > > > > > There are some ideas presented for GSOC 2015 here > > > https://nixos.org/wiki/GSOC_2015_ideas_list, my fave is P2P substitutes. > > > This would mean it would be easy to share a cache and in some cases > > > improve > > > speed. Maybe not all features are needed for this project. For example, a > > > interface where you can control what to seed can be added later on. > > > > > > In the end I think you should choose what you think will be most fun or > > > the project that you think will make nix or nixos stronger. Good luck :) > > > > > > On Thu, Oct 29, 2015 at 9:01 AM, Matthias Beyer <m...@beyermatthias.de> > > > wrote: > > > > > >> Hi, > > >> > > >> for those who don't know me: I'm a 24 year old student at a university > > >> of applied sciences in the black forest, germany. I'm in my 6th > > >> Semester right now, the 7th (bachelors thesis) starting in > > >> Feb/March 2016. > > >> > > >> I'm writing you people because there might be ideas for a > > >> NixOS-related bachelors thesis? > > >> > > >> The constants are: > > >> > > >> - Time: Something 4-month-is > > >> > > >> - I don't want to do it at a company and I want to remain at my > > >> university for the time of the thesis, if possible. Also because > > >> I still want to attend some (voluntary) lessons there > > >> > > >> - The topic should be NixOS related (personal interest), I have to > > >> convince my professor, though > > >> > > >> - It should be programming-related > > >> > > >> - I want to be able to create, I want to be able to be creative > > >> > > >> - I want to be able to choose the language I program in, if > > >> possible. Candidates are: > > >> > > >> - C (not unconditionally) > > >> - C++ (I'm not so good at it) > > >> - Ruby (I'm really good, I guess) > > >> - Bash (I'm okay at it) > > >> > > >> - I can relate to the topic. I have no personal use for nixops and > > >> therefor never used it, so I won't have any relation to a > > >> nixops-related topic... I guess you understand what I mean here. > > >> > > >> I guess there are more things to this list and I just cannot remember > > >> them right now. > > >> > > >> I already had an idea, where a prof told me that he would do this and > > >> the scope is okay for a thesis at a university of applied sciences: > > >> > > >> The idea was to create a source-to-source compiler and translate > > >> (for example) Archlinux pkgbuild files to nix expressions. > > >> > > >> There would be three steps in complexity: > > >> > > >> Simple: compile one package to one package. Just AST > > >> transformation, nix files have to be manually edited > > >> afterwards, eventually > > >> > > >> Medium: compile a tree of packages (optionally find cyclic > > >> dependencies), nix files have to be manually edited > > >> afterwards, eventually > > >> > > >> Complex/Large: compile a tree of packages, find cy
