Linux installation

[anton....@gmail.com]

Hello everyone.

---

tlrd:

Linux installation is in bad shape.
I expanded script and solver bugs to make better installation.
https://github.com/NixOS/nix/pull/1565
It got big, because small PR stuck. Seems like team doesn't have active human that responcible for Linux shell installation part.
I am happy to work with, be reviewed, or maintain Linux shell installation part.

Thant you.

Even recorded video demonstration:

Video where I show the current UX of installation and points I am solving:
https://www.youtube.com/watch?v=NuyevCXBqyY
I show exerience if Linux user or speciallists installs Nix. And Nix installer needs workarounds and 5 installation restarts.

Video demonstration of improved version:
https://www.youtube.com/watch?v=yD3pgkMvuGw
Where I show much smoother experience for new user/DevOps of installing Nix on Linux.
Solved major installation bugs of script, and script is much more user friendly and automatic.
Basicly just pouring work on script install.

Script is POSIX standart compatible, uses plain sh and The Syslog Protocol loglevels message classification [RFC 5424](https://tools.ietf.org/html/rfc5424#section-6.2.1)
Script was tested in different setups, on different distributions.
If there is suggestions, especially regarding other recommendations and standarts, I am happy to have responce.

---

I devoted a couple of days to work on improving Linux setup of Nix.

I solved most preassumptions of Nix installation procedure, and streamlined it in my local version.
I submitted first simple pull requests. But they not get merged.

While install Nix on clean Ubuntu, Arch Linux and Alpine Linux (this is just what I've tried) not working, not without manual troubleshooting.
Obviously on other distributions the same.

Cureent master script assumes:

* you are not root
* you are runing it basically on a Linux desktop disrtibution
* you not running it in Docker
* user has sudo installed
* user has sudo access
* system have `nixbld` group already somehow
* and `workers` (nixbldN) already exist (even while Linux install does single-user setup)
* parts of script assumes you are usin Bash.

Doesn't that reminds you something. Maybe some particular setup?

I also had problem building it from source on Arch Linux. Some dependency mentions missing.

I am also current maintainer of Nix package on Arch Linux. That is why I come to you.

My initial three pull requests with Linux install shell code, got reviewed by three different people. And not merged. That is really bare-bone inprovements.
I see situation as: there is no active maintainer of Linux insallation, so everyone comments and waits on someone other to merge commits. And seems there is no active human that has and ready to take responcibility to currate and accept Linux install code.

I test before submitting.
Stable Nix was released recently.
That means this is a perfect window to make changes to master install progress and get additional development responces.

About me

I am Linux maniac for 10 years. And a DevOps. I live 24/7 seven with my Linux systems.
About shell. I've done shell projects for production and financial data before (that was one project, with those crazy requirements, to program all through shell. I even done GUI through shell tools).
And shell is most usable language for me today.

Goals:
I aim to make install automatic, clean, beautiful, verbose, corresponding to industry standarts and level, and portable (POSIX compatible, and working on most Linux evironments).

I am happy to cooperate in code with other contributors.

I have time to take on myselt the Linux install code part and be responcible to maintain it.


Hope someone helps me to push progress in master and we get process moving/evolving further.
Thank you.

Anton Latukha

[Wout Mertens]

Hi Anton,

(Please note that somehow, your email didn't render by default in Google Inbox and I had to use "view full email" to read it.)

I will look at your PR for commenting, but the problem is that this is `nix` code, not nixpkgs, and Eelco is the only one that can merge there and he is always very uncommunicative about PRs. If he doesn't like a PR he will just say nothing or maybe a small comment and not merge it.

Wout.

On Sat, Sep 9, 2017, 7:49 PM <anton....@gmail.com> wrote:

[Ivan Lazar Miljenovic]

On 11 September 2017 at 14:49, Wout Mertens <wout.m...@gmail.com> wrote:
> Hi Anton,
>
> (Please note that somehow, your email didn't render by default in Google
> Inbox and I had to use "view full email" to read it.)

I think that's because of the "..." at the beginning, which GMail
interprets as "Signature follows".

>
> I will look at your PR for commenting, but the problem is that this is `nix`
> code, not nixpkgs, and Eelco is the only one that can merge there and he is
> always very uncommunicative about PRs. If he doesn't like a PR he will just
> say nothing or maybe a small comment and not merge it.
>
> Wout.
>
> On Sat, Sep 9, 2017, 7:49 PM <anton....@gmail.com> wrote:
>

> --
> You received this message because you are subscribed to the Google Groups
> "nix-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nix-devel+...@googlegroups.com.
> To post to this group, send email to nix-...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nix-devel/CAO3V83JKXx0WcxFrjcE8qgE0-XqSNjPzLVR7UNyXPGL6bWirsg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



--
Ivan Lazar Miljenovic
Ivan.Mi...@gmail.com
http://IvanMiljenovic.wordpress.com

[anton....@gmail.com]

Yeah.

I probably bothered him too hard too much in the last week. Polemicizing him with my arguments.

 

This is a thing with creators in Open Source projects.
I worry if he is not in some stage of burnout.

 

This is known problem, creator of Python Djando framework gave presentation on that: https://www.youtube.com/watch?v=EqcuzSwySR4

Conference name may seem laughable.

But his presentation legitimately tells us his story and describes a common situation in an Open Source project, when it becomes popular and growth of community happen.
In Python Djando story, he stayed up with the project for 9 years, before he can no more.

 

Since Linux installation in master is legitimately not in ideal state...

Eelco really seems not receptive to contributions there somehow and for some reason.

BTW I've seen you synced one time Linux script with rest of the project, ans that solved a bunch of bugreports.

 

I don't know. I going to try.

I am not a fan of a future where we stack developer blobs of Ubuntu runtime on top of one another in distros (snaps), and neglecting maintainability and dependency control.

 

I want Nix to take the future of Linux packaging, but without advancement of introduction/installation quality and therefore - adoption - when Nix is going to get to the line, world will move on from Linux platform because of software shit show in Linux, and not effective community fragmentation. Nix provides unified ground to gather both developers and distribution maintainers in one Linux community.

Othervise snaps and flatpacks get adopted in distributions and as a defacto platform to deliver products.

 

If Nix advances now - now is the time, Nix wins; to transform Open Source.

 

Anton

[Peter Simons]

Folks,

please cut out any speculation about the emotional state of another
contributor to this project. That kind of gossip does not belong on this
list. It is terribly rude to talk about someone in the 3rd person who is
clearly listening. This forum is intended for discussing the Nix
project. It is not intended for discussing Nix contributors.

Best regards,
Peter

[anton....@gmail.com]

Peter.

You are right. I am partially rude.

Partially, I am noone here, so I am as a royal jester, can say to the King the things others can't dare.

You can treat me as not serius.

Gossip - is to not say, and let gossip rise by itself. And to close eyes when everyone needs to call him personally, when he also at the same time works the hardest, and look at that like it's normal.

Ok. I shut up, and I see no point to say more.