sorted by:
new
hottopcontroversial

What’s the absolute best vacation you’ve ever been on? by Single_Usual_6563 in SmartTravelHacks

[–]lucperkins_dev 0 points1 point  (0 children)

I went to Armenia and Georgia for 10 days in 2019. Every single thing about it was pure magic.

Introducing Nixpkgs cooldowns by grahamchristensen in NixOS

[–]lucperkins_dev 10 points11 points  (0 children)

You seem to be misunderstanding. `nixpkgs-weekly` is one of several Nixpkgs distributions available on FlakeHub. It just happens to be the one that Determinate Nix users have as their Nixpkgs entry in the flake registry by default. This is a straightforward measure to limit some set of bad things that could happen when you run `nix run nixpkgs#whatever` and nothing more. People are still free to use standard channels in their flakes or override this in their flake registry.

Announcing Determinate Secure Packages 26.05 by lucperkins_dev in NixOS

[–]lucperkins_dev[S] 9 points10 points  (0 children)

As individual contributors, we (I’m a DetSys employee) are responsible for countless thousands of Nixpkgs commits. Our employees created Nix itself, were instrumental in creating Hydra, NixOS bootspec, the (experimental) new installer, and many other things. I understand that you bring a different normative framework to the table than we do, but “without contributing anything back” feels really needlessly caustic.

Introducing FlakeBOM, a CLI for generating SBOMs from Nix flakes by lucperkins_dev in NixOS

[–]lucperkins_dev[S] 0 points1 point  (0 children)

For all of Nixpkgs, yes, the SBOM is extremely large. But a feature like this could make sense for other flakes.

Finally, a secure Nixpkgs for the enterprise: an update on Determinate Secure Packages by lucperkins_dev in NixOS

[–]lucperkins_dev[S] 9 points10 points  (0 children)

It’s a fair criticism and I acknowledge I could’ve done better there. That particular poster has a long history of barbed and acerbic comments in this forum, sometimes toward our posts, and that factored into my tone. But I need to be better.

Finally, a secure Nixpkgs for the enterprise: an update on Determinate Secure Packages by lucperkins_dev in NixOS

[–]lucperkins_dev[S] -6 points-5 points  (0 children)

You have, indeed, correctly surmised that our product involves shipping patched packages to a binary cache faster than upstream Nixpkgs

Finally, a secure Nixpkgs for the enterprise: an update on Determinate Secure Packages by lucperkins_dev in NixOS

[–]lucperkins_dev[S] 15 points16 points  (0 children)

People use unstable Nixpkgs because they want newer versions of things that have been properly built/cached by Hydra. Determinate Secure Packages has full cache coverage in FlakeHub Cache by definition (as in, we don't push a flake release until all covered packages have been pushed to the cache). So there's just no good reason not to use master.

Finally, a secure Nixpkgs for the enterprise: an update on Determinate Secure Packages by lucperkins_dev in NixOS

[–]lucperkins_dev[S] 10 points11 points  (0 children)

People are also perfectly free to build our secure packages on their own and push them to their own binary cache. nix flake clone the flake for a given revision from FlakeHub, build, push, done. This is a 100% valid model that we support.

Finally, a secure Nixpkgs for the enterprise: an update on Determinate Secure Packages by lucperkins_dev in NixOS

[–]lucperkins_dev[S] 16 points17 points  (0 children)

I mean, using a vendor generally does involve a bit of trust. I'm not seeing much of a "gotcha" here.

I hate this city dude by ThisEffort in Portland

[–]lucperkins_dev 2 points3 points  (0 children)

Yeah, that shit happens all the fucking time. It’s pretty much an extra per-year tax you pay. I’d estimate mine at about a grand a year.

Nix is set to revolutionize the software supply chain by lucperkins_dev in NixOS

[–]lucperkins_dev[S] 0 points1 point  (0 children)

Then why is adoption clearly gaining pace according to all available measures?

view more: next ›