[Nix-dev] Google Summer of Code 2017

[David Izquierdo]

Oh dear, I had been thinking about 1 and 2 lately...


On systemd, I don't think that it's worth it to even try to port 
dependent software. Nix is smart enough to warn about/fix dependencies. 
And "porting" the actual unit files sounds easy IMO, systemd has good 
documentation on unit files that can be easily mapped to alternative 
complementary software (one example I've used recently: `timeout` 
instead of "RuntimeMaxSec"). I don't think indirection would be 
necessary, since the declarative style of units is already really really 
nice to us. Simply moving the relevant options out of the systemd 
namespace and into a more general place (services.service.$NAME?).


BSDs... I thought they had official support... They don't, according to 
the Nix manual's Supported Platforms chapter. I guess once it exists AND 
systemd becomes optional, it's solved itself. And I don't see why Nix 
wouldn't just-work on a BSD when it's supported on Linux and MacOS.


Now, literally all of the above has been pulled out of my backend, and 
from a few months worth of NixOS usage and learning. I hope someone with 
actual knowledge can fix this, and better outline how deep into NixOS's 
internals one would have to plumb to implement this.


On 13/03/17 18:23, Anderson Torres wrote:
> 2017-01-08 18:40 GMT-02:00 Profpatsch <mail at profpatsch.de>:
>> 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...
> I would suggest three big fat proposals:
>
> 1 - The most flamewar-igniting one: getting rid of systemd dependency!
> It would be very nice if the init system was selectable, with a sane
> default (as openrc).
> It would be hard as hell to port certain software as Gnome stack, but
> I think it can be solved.
>
> 2 - Another for the even more courageous would be run a Nixos+kNetBSD
> (or kFreeBSD), as in Debian. It would be the definitive test for
> portability and independence of Nix model.
>
> 3 - Another set of defaults for the stdenv, as musl+clang.
>
>> 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 at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev