Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 07dfecdc5f5bcee3fb12c3385673f766aa1a
https://github.com/NixOS/nixpkgs/commit/07dfecdc5f5bcee3fb12c3385673f766aa1a
Author: Bart Brouns
Date: 2017-01-13 (Fri, 13 Jan 2017)
I agree with zimbatm. I find the GUIX posts very topical and heavily
geared towards my perceived notion of this mailing-list's mission
(although I'm currently just lurking to hone my Nix).
I admit that I have not looked into fractalide, which could very much
be topical, however some form of
Hi community.
I just ordered a XIDO Z120 Tablet with the idea to try to get NixOS on
it working, over the next few months, ... as an early summer-project.
If you have _any_ input, I would highly value some short notes how to
do it!
I will, of course, publish the results of my research on my
Hi Domen,
I do not use the stable releases, but I highly value that we have them
anyways, so I wanted to say: Thank you very much for helping NixOS and
its community!
Lets hope we find a successor!
Matthias
On 06-01-2017 19:23:35, Domen Kožar wrote:
> Hi all,
>
> due to following reasons I
Thu 12 Jan 17 − 15:13, Profpatsch(m...@profpatsch.de) a écrit:
> 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
Hi,
For my own curiosity: Is your adviser's work online somewhere?
~
On 12 January 2017 at 17:17, Théophane Hufschmitt
wrote:
> Thu 12 Jan 17 − 15:31, Peter Simons(sim...@nospf.cryp.to) a écrit:
> > Hi Théophane,
> >
> > > https://www.gofundme.com/typing-nix
> >
> > I
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: da563e5773be82c56d8ad2855f49b299c21aa2d1
https://github.com/NixOS/nixpkgs/commit/da563e5773be82c56d8ad2855f49b299c21aa2d1
Author: Johannes Bornhold
Date: 2017-01-12 (Thu, 12 Jan
Thu 12 Jan 17 − 18:30, Michael Raskin(7c6f4...@mail.ru) a écrit:
> >I agree with your concerns about the separate implementation.
> >The reason for this is related to your third paragraph. The inference
> >algorithm that is going to be used is no trivial at all to implement,
> >and my advisor
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: cb4ebb6749f1256bb014afc3225b0542f5da32b6
https://github.com/NixOS/nixpkgs/commit/cb4ebb6749f1256bb014afc3225b0542f5da32b6
Author: Kier Davis
Date: 2017-01-12 (Thu, 12 Jan 2017)
Thu 12 Jan 17 − 19:36, Profpatsch(m...@profpatsch.de) a écrit:
> 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
Branch: refs/heads/release-16.09
Home: https://github.com/NixOS/nixpkgs
Commit: 7b34209e1bb5d38106115e52506a2ed777608672
https://github.com/NixOS/nixpkgs/commit/7b34209e1bb5d38106115e52506a2ed777608672
Author: Peter Simons
Date: 2017-01-12 (Thu, 12 Jan 2017)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: d483a871d1bc9a7c2c719dad976ba343cd1a21dc
https://github.com/NixOS/nixpkgs/commit/d483a871d1bc9a7c2c719dad976ba343cd1a21dc
Author: Tim Steinbach
Date: 2017-01-11 (Wed, 11 Jan 2017)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 60435691f78dc533d49bf30751e1a8328b67367a
https://github.com/NixOS/nixpkgs/commit/60435691f78dc533d49bf30751e1a8328b67367a
Author: Domen Kožar
Date: 2017-01-12 (Thu, 12 Jan 2017)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 2fd0a9f3c74a29e87952c7657aed8194258a83c4
https://github.com/NixOS/nixpkgs/commit/2fd0a9f3c74a29e87952c7657aed8194258a83c4
Author: Peter Simons
Date: 2017-01-12 (Thu, 12 Jan 2017)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 086fbfa3088defd3e6b0278161cdca792f1bd704
https://github.com/NixOS/nixpkgs/commit/086fbfa3088defd3e6b0278161cdca792f1bd704
Author: Vincent Laporte
Date: 2017-01-12 (Thu, 12 Jan
On Thu, Jan 12, 2017 at 7:03 PM, Profpatsch wrote:
> Not sure what this has to do with nix-dev?
tough crowd, tough crowd.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
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.
>> please speak for yourself. I found Stewart's message both interesting
>> and relevant for this mailing list -- much more so than the trolling and
>> flaming that followed it. I did not respond simply because I had nothing
>> meaningful to say, so please don't include me in that "us" crowd that
Interesting idea.
Note that Eelco's phd thesis about nix contains a formal definition of both
the syntax and semantics the language.
The whole thesis is well written and approachable.
Potential other benefits from a deeper analysis could include:
- generation of better documentation for helper
stewart mackenzie writes:
> Reusable Functions - They're great, they're just great, you'll love them.
Sneaky remarks like this are totally inappropriate here. Profpatsch
asked nicely for a short pitch of your project, and you throw this
completely useless sentence into his
Hi Théophane,
> https://www.gofundme.com/typing-nix
I see that you plan to spend approx. 2 months (a third of the entire
project's time) on developing a parser for Nix. Why do you feel that
this is necessary, considering that there is a parser for Nix already?
The notion of working with a
>Note that Eelco's phd thesis about nix contains a formal definition of both
>the syntax and semantics the language.
But remember that it contains a formal definition of the language at the
moment when the thesis has been written (obviously), and the current
state of NixPkgs and NixOS relies on
Hi,
Many thanks for giving this a shot, it's exciting! I donated some money and
I hope we'll get this rolling soon.
I have a few questions:
* Is the plan to merge this into the current nix c++ code base? If so: Do
you have some buy-in from the nix maintainers?
* If it's an external tool: would
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 167795cd159336f64ce2e8fbde6a3819b0b81fd5
https://github.com/NixOS/nixpkgs/commit/167795cd159336f64ce2e8fbde6a3819b0b81fd5
Author: Reno Reckling
Date: 2017-01-11 (Wed, 11 Jan 2017)
2017-01-12 13:20 GMT+01:00 stewart mackenzie :
>
> Reusable and reproducible functions have nothing to do with Nix/NixOS?
>
Not in particular with nix-dev, they don't.
What about reproducible libraries?
>
Nope.
> What about reproducible monolith apps?
>
No. Why not try
stewart mackenzie writes:
> Nix's very existence revolves around solving an insanely hard problem,
> that of reproducibility, it's the only project that actually gets it
> right.
> Reproducible monolith apps have _everything_ to do with Nix/NixOS
> Reproducible libraries have
2017-01-12 14:48 GMT+01:00 Peter Simons :
>
> please speak for yourself. I found Stewart's message both interesting
> and relevant for this mailing list -- much more so than the trolling and
> flaming that followed it. I did not respond simply because I had nothing
>
On Thu, Jan 12, 2017 at 8:46 PM, Herwig Hochleitner
wrote:
> ...
Nix's very existence revolves around solving an insanely hard problem,
that of reproducibility, it's the only project that actually gets it
right.
Reproducible monolith apps have _everything_ to do with
> What about guix https://www.gnu.org/software/guix/ ?
> Does some typing exist here already?
There exist things (which are among the stuff I plan to study before
designing the system) for scheme
(like http://www.ccs.neu.edu/racket/pubs/popl08-thf.pdf), but as far
as I know, nothing special to
So let me understand this clearly.
Reusable and reproducible functions have nothing to do with Nix/NixOS?
What about reproducible libraries?
What about reproducible monolith apps?
This is a _new_ concept to the Nix/NixOS
___
nix-dev mailing list
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: adbc201147a1c2852c5cb1601e62bfb9c734fc5c
https://github.com/NixOS/nixpkgs/commit/adbc201147a1c2852c5cb1601e62bfb9c734fc5c
Author: Michael Alan Dorman
Date: 2017-01-11 (Wed, 11
Hi Shea,
This probably won't have a huge interest for stuff like updating
packages (or adding new one), as those are indeed more "scripting",
with almost no interaction with the rest of the repo (but still, typed
scripting is cool :) )
It becomes however much more useful when dealing with big
Hi Herwig,
> Profpatsch is actually being quite courteous by politely pointing out
> that your message fails to be relevant to nix-dev, instead of
> ignoring you, like the rest of us do.
please speak for yourself. I found Stewart's message both interesting
and relevant for this mailing list
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
Reusable Functions - They're great, they're just great, you'll love them.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Branch: refs/heads/release-16.09
Home: https://github.com/NixOS/nixpkgs
Commit: bb452bcb44b9807a1d1a19e2c93967ff3254a689
https://github.com/NixOS/nixpkgs/commit/bb452bcb44b9807a1d1a19e2c93967ff3254a689
Author: Peter Hoeg
Date: 2017-01-12 (Thu, 12 Jan
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: ef318d01e999390337a9b6b8883382550b929cf0
https://github.com/NixOS/nixpkgs/commit/ef318d01e999390337a9b6b8883382550b929cf0
Author: Peter Hoeg
Date: 2017-01-12 (Thu, 12 Jan 2017)
Hi,
I am Théophane Hufschmitt, a french master degree CS student, and I
wish to start a six month length internship on giving nix a type
system.
Numtide offered to fund a part of the internship, but we still need
some help for me to be able to start it.
The goal of the internship is to design
> Can you give a specific case where your type system would improve things
> for either users or developers of nixpkgs? In my experience most of the
> nix "code" I write is really just declaration or bash programming, and
> it's not clear to me how different types would help.
Have you never
2017-01-12 12:08 GMT+01:00 stewart mackenzie :
> On Thu, Jan 12, 2017 at 7:03 PM, Profpatsch wrote:
> > Not sure what this has to do with nix-dev?
>
> tough crowd, tough crowd.
>
Hi Stewart,
Profpatsch is actually being quite courteous by politely
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: e91840cfb6b7778f8c29d455a2f24cffa1b4e43e
https://github.com/NixOS/nixpkgs/commit/e91840cfb6b7778f8c29d455a2f24cffa1b4e43e
Author: Daiderd Jordan
Date: 2017-01-12 (Thu, 12 Jan 2017)
Hi Théophane,
Can you give a specific case where your type system would improve things
for either users or developers of nixpkgs? In my experience most of the
nix "code" I write is really just declaration or bash programming, and
it's not clear to me how different types would help.
Thanks,
Shea
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
Branch: refs/heads/release-16.03
Home: https://github.com/NixOS/nixpkgs
Commit: 5f94adc9183c429ba78f474513b93afcad5bc4d9
https://github.com/NixOS/nixpkgs/commit/5f94adc9183c429ba78f474513b93afcad5bc4d9
Author: Domen Kožar
Date: 2017-01-12 (Thu, 12 Jan 2017)
Branch: refs/heads/release-16.09
Home: https://github.com/NixOS/nixpkgs
Commit: 67b2c9419d0b5d13641d4895ad0eafd79be4db57
https://github.com/NixOS/nixpkgs/commit/67b2c9419d0b5d13641d4895ad0eafd79be4db57
Author: Domen Kožar
Date: 2017-01-12 (Thu, 12 Jan 2017)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: e5dcce837a1a59491e1fc2bc6a479c1c51e2dfe0
https://github.com/NixOS/nixpkgs/commit/e5dcce837a1a59491e1fc2bc6a479c1c51e2dfe0
Author: Domen Kožar
Date: 2017-01-12 (Thu, 12 Jan 2017)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 45a677b978bd9b1d648a9b455b482dff514f24fb
https://github.com/NixOS/nixpkgs/commit/45a677b978bd9b1d648a9b455b482dff514f24fb
Author: Domen Kožar
Date: 2017-01-12 (Thu, 12 Jan 2017)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: befc29454b6057969ebfc3cbd338c2e55d94114f
https://github.com/NixOS/nixpkgs/commit/befc29454b6057969ebfc3cbd338c2e55d94114f
Author: Vincent Laporte
Date: 2017-01-12 (Thu, 12 Jan
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: ac0b6b9a2cc7940de276fa3cb7afde80e14b5d6b
https://github.com/NixOS/nixpkgs/commit/ac0b6b9a2cc7940de276fa3cb7afde80e14b5d6b
Author: Volth
Date: 2017-01-12 (Thu, 12 Jan 2017)
Changed
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
Hi Maarten,
I plan to rely heavily on Eelco's thesis for rewriting the spécifications, but
it will need a serious update because of the changes that happened to the
language.
Integration into an ide is a long term goal, but this is probably not gonna
happen anytime soon. (but using types to
>I agree with your concerns about the separate implementation.
>The reason for this is related to your third paragraph. The inference
>algorithm that is going to be used is no trivial at all to implement,
>and my advisor already has done a lot of work on this that could be
>reused, but written in
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: f4bed1e06ebfeaa9bb20ae00d707d1eafb67e219
https://github.com/NixOS/nixpkgs/commit/f4bed1e06ebfeaa9bb20ae00d707d1eafb67e219
Author: Vincent Demeester
Date: 2016-11-10 (Thu, 10 Nov 2016)
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: cb6f49a61f9879e3ec652971e44ca3afbc716d12
https://github.com/NixOS/nixpkgs/commit/cb6f49a61f9879e3ec652971e44ca3afbc716d12
Author: Vladimír Čunát
Date: 2017-01-12 (Thu, 12 Jan 2017)
Branch: refs/heads/release-16.09
Home: https://github.com/NixOS/nixpkgs
Commit: d05b50229b80ef9c091445e83bdc0dad23661c23
https://github.com/NixOS/nixpkgs/commit/d05b50229b80ef9c091445e83bdc0dad23661c23
Author: Vladimír Čunát
Date: 2017-01-12 (Thu, 12 Jan
Hi Thomas,
Thanks for the donation :)
I don't plan to try making this builtin into the nix codebase (at least not
for now) for several reasons, essentially :
- As I explained to Peter, the code will be in OCaml, so it won't be
mergeable at all.
- The tool will probably only be useful for nix
Thu 12 Jan 17 − 15:31, Peter Simons(sim...@nospf.cryp.to) a écrit:
> Hi Théophane,
>
> > https://www.gofundme.com/typing-nix
>
> I see that you plan to spend approx. 2 months (a third of the entire
> project's time) on developing a parser for Nix. Why do you feel that
> this is necessary,
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 9c489165af0f259e48eed0427df5b2498b813b38
https://github.com/NixOS/nixpkgs/commit/9c489165af0f259e48eed0427df5b2498b813b38
Author: Volth
Date: 2017-01-12 (Thu, 12 Jan 2017)
Changed
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 05bb3fe22e2cfa47a77fa44e278b78e6f21e988f
https://github.com/NixOS/nixpkgs/commit/05bb3fe22e2cfa47a77fa44e278b78e6f21e988f
Author: Bjørn Forsman
Date: 2017-01-12 (Thu, 12 Jan
Branch: refs/heads/release-16.09
Home: https://github.com/NixOS/nixpkgs
Commit: 0f586281029822293b942398566f20c56e729fc4
https://github.com/NixOS/nixpkgs/commit/0f586281029822293b942398566f20c56e729fc4
Author: Bjørn Forsman
Date: 2017-01-12 (Thu, 12
Ironically I didn't get the original message but now have 10 more emails to
read, not all of them super friendly. As far as I know there are no
explicit rules for the mailing list so it's open for interpretation. If we
want to set more rules then we need a document that we can refer people to,
and
61 matches
Mail list logo