Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Nixpkgs core team has disbanded

discourse.nixos.org

Post reply on HN
Print view View original

211–220 of 220 posts

Re: The Nixpkgs core team has disbanded

#211

Post by lrvick »

nextaccountic wrote: post #167
lrvick wrote: post #144

Earlier quoted context omitted.

Both statements are valid for StageX

How to define the list of installed packages in a config file in StageX, and tell the system that it should be the new list of packages? Like done in nixos If I remove a package from the list itt best uninstalled, if I add it gets installed, etc

https://git.distrust.co/public/airgap/src/branch/main/Contai...

That containerfile defines an entire deterministic custom OS image, every package, and every configuration etc.

Many patterns are possible, though this will be made way easier with our upcoming "box" primitives

Re: The Nixpkgs core team has disbanded

#212

Post by lrvick »

alberth wrote: post #204
nextaccountic wrote: post #167

Earlier quoted context omitted.

How to define the list of installed packages in a config file in StageX, and tell the system that it should be the new list of packages? Like done in nixos If I remove a package from the list itt best uninstalled, if I add it gets installed, etc

Agreed, with NixOs - not only can you declare which packages to include, you can declare how those packages are setup. Like setting up nginx as a package with SSL support for example.com domain, PHP working with nginx via PHP-FPM, etc. StageX I don’t believe can do that. I believe it can only confirm that the nginx package hasn’t been tampered with.

Thats just all stuff one puts in a containerfile that generates their disk image. We can build any disk image nix can though with different syntax.

Re: The Nixpkgs core team has disbanded

#213

Post by stevefan1999 »

otabdeveloper4 wrote: post #96
XorNot wrote: post #88

Earlier quoted context omitted.

For a certain definition of "correctly" (namely: it doesn't, it just does what containers do and ships unique versions for every package).

Containers don't solve dependency hell. They just give you a standard way to ship your bespoke bash scripts. If you like writing bash scripts then go for it. (Personally I'd rather be doing literally anything else, like, I don't know, shoveling manure.)

Containers do solve dependency hell by isolation. It's like venv/uv in Python that you switch between different environment with different sets of dependency. Or speaking essentially, you lifted yourself away from having dependencies shenanigans since you have virtualizations of it

Re: The Nixpkgs core team has disbanded

#215

Post by forrestthewoods »

hugmynutus wrote: post #148
forrestthewoods wrote: post #123

Earlier quoted context omitted.

My gut feeling is that Nix is just not quite the right abstraction level. I can’t quite articulate this. And hell maybe I’m wrong. I don’t want to configure a global environment. I just want a build system that works reliably in any environment and can cross-compile from any platform to any platform. Nix does too damn much. All I want is a build system that doesn’t suck. And I want to run it on windows + Mac + Linux…

Shared Dynamic Libraries. Not to say they aren't useful. Keeping applications small, keeping security updates simple, sub linear ram scaling, yada-yada-yada, big wins cross the board, not debating that. The pervasive link detection structure of effectively everything on GNU/Linux assumes is (more-or-less) objectively incorrect behavior in any sane security minded context. Binaries should be able to declare the interf…

> lipstick on a pig

Yes!!

> dancing around the core issue that `foo.exe` cannot ever realize `foobar-v1.8` and `foobar-v1.7` are both installed on the same computer

I’m curious if you have an opinion on how you think this should be handled?

At this point I’m just on team static linking or Windows DLL black box style. The Linux approach of dynamic libraries which function same as static is just the worst of every world.

I also blame C/C++ toolchains for being very very bad on Linux.

Re: The Nixpkgs core team has disbanded

#216

Post by toshinoriyagi »

Pay08 wrote: post #205
embedding-shape wrote: post #158

Earlier quoted context omitted.

> NixOS is dying, everyone sees this right now. Huh? Based on what? The packages I use keep getting updated, so clearly nixpkgs is alive. The OS I use keep getting updated, so clearly NixOS is alive to. Who exactly is dying, and what makes you believe that?

Isn't nixpkgs still a pretty bad state? I know there used to be a lot of "abandoned" packages that went years without updating to the new versions provided by upstream, that a lot of packages were copying binaries around instead of building open source software from the source, etc.

Nixpkgs is one of, if not the largest, package managers by # of packages. I think naturally that will result in more abandoned packages than others. What is the % of abandoned packages relative to total I can't say.

Nix tends to have updates almost as quickly as Arch does, I run a lot of bleeding edge software and have no issues, and the breadth of packages is immense. Nix just has a different style. With the AUR, you can adopt an abandoned package more easily. That has pros and cons (the AUR has recently suffered multiple supply-chain attacks due to packages being adopted and infected).

Re: The Nixpkgs core team has disbanded

#217

Post by frantathefranta »

shakna wrote: post #199
frantathefranta wrote: post #188

Earlier quoted context omitted.

Yes, I do believe not having a pfp at all would be better (for disclosing CVEs or sharing a statement about disbanding the nixpkgs team). By all means use any pfp for normal forum purposes.

I'm afraid at this point, that sounds more like a you problem. You're judging people for something inconsequential. Your reasons are your own but... Probably worth some introspection here.

I'm very well aware it's a me problem, anime just isn't for me and it's super popular. I'm honestly surprised that a single person seemed to agree with me.

Re: The Nixpkgs core team has disbanded

#218

Post by nickdichev »

Pay08 wrote: post #205
embedding-shape wrote: post #158

Earlier quoted context omitted.

> NixOS is dying, everyone sees this right now. Huh? Based on what? The packages I use keep getting updated, so clearly nixpkgs is alive. The OS I use keep getting updated, so clearly NixOS is alive to. Who exactly is dying, and what makes you believe that?

Isn't nixpkgs still a pretty bad state? I know there used to be a lot of "abandoned" packages that went years without updating to the new versions provided by upstream, that a lot of packages were copying binaries around instead of building open source software from the source, etc.

A common pattern is to manage your own "overlay" repo on top of nixpkgs to keep the packages you care about up to date.

Re: The Nixpkgs core team has disbanded

#219

Post by aktau »

talentedcoin wrote: post #46
aroman wrote: post #43

Earlier quoted context omitted.

What alternative have you moved on to?

I suggest giving Bazzite a try

Much more resource heavy. I tried NixOS and Bazzite (and other spins purporting to be lighteweight) and the difference on a 2010-era mid-range laptop was noticeable in terms of sluggishness. Not that this laptop was going to be my daily driver, but I like experimenting. It was a good showing for NixOS and that decided which one I would take. All of the other nice things about NixOS (fast rebuilding, easy install images, remote deploy, easy build tweaks, ...) were cherries on top.

Re: The Nixpkgs core team has disbanded

#220

Post by nextaccountic »

lrvick wrote: post #211
nextaccountic wrote: post #167

Earlier quoted context omitted.

How to define the list of installed packages in a config file in StageX, and tell the system that it should be the new list of packages? Like done in nixos If I remove a package from the list itt best uninstalled, if I add it gets installed, etc

https://git.distrust.co/public/airgap/src/branch/main/Contai... That containerfile defines an entire deterministic custom OS image, every package, and every configuration etc. Many patterns are possible, though this will be made way easier with our upcoming "box" primitives

There is a lot of repetition/stutter, also there's some hashes that belong to a .lock file. Is there tooling to edit this file? (Like some command to add/remove/update entries)

Is this what the box primitives is about?

Post reply on HN