Logs? Fuck that! Here's a big tux for you to enjoy scream at. Truly genius idea to associate tux with failure.
- Posts
- 89
- Comments
- 1514
- Joined
- 3 yr. ago
- Posts
- 89
- Comments
- 1514
- Joined
- 3 yr. ago
To answer your question: no guideline (as is typical with nix).
I always check https://search.nixos.org/options first. There's a chance it's a package which requires setup or even a service that has extra config. If it's not there, then https://search.nixos.org/packages is next.
When multiple come up, it depends which prefix or suffix they have. Prefixes like
pythonPackages.either mean the package is written in a specific programming language with its own packaging intricacies and its easier to keep them under that prefix, other prefixes likeneovimPackages.mean it's a package for a program and something like a plugin or so. Probably more prefixes exist.There are some agreed upon but badly documented suffixes (the usual nix style). But if it's a version suffix, then it's up to you to decide which one to use. In a comment you mentioned
julia, well that's a programming language so you have to choose the version you want. Sometimes the manual has information on how to use the programming language or one of the wikis.So inherently IPFS has nothing to do with crypto, but people read about some external connection and now thing it's crypto or something... Sounds typical.
What does crypto have to do with IPFS tech? I installed IPFS and nowehere does it mention crypto.
If you feel that “open source”, as per the OSD, has to change, I’d ask why does it need to change instead of you using an alternative term
Simple: OSI doesn't own the word "open source", nor should they. Their definition is as blue eyed and naive as Marxism. It doesn't evolve nor live in the real world, but a one of fantasy where no method of exploitation nor circumvention has been invented. It's basically a world where lying hasn't been invented.
In our real world with real consequences and real people, companies take advantage of opensource. The vast majority of open source maintainers and authors can't live on open source. Yet somehow the privileged few that can, would like to make everyone believe that principles pay off, and that living by some definition made by the privileged is the only " right way" to make a living writing opensource.
I find it to be nearly in the same vein as rich people who say "if you work hard enough, you can be rich like me" and throw around platitudes like "pull yourself up from your bootstraps". Or being like those in an ivory tower judging those trying to find a way to make a living: " no, not like that! only my way is just".
My bad.
I'm not trying to make a case for the licence. I'm just adding it to my comments yet people keep feeling it necessary to harass me about it. The list of people I've blocked for mocking me about it has become quite long. Should I start reporting them?
You're annoying and pointless.
Here are the basic steps though:
- package the target in a derivation aka a recipe to package the thing you like
- test it in a
nix-shellor add it straight to yourconfiguration.nix
I know it sounds a lot like
, but a few pointers:Derivation basics: This wiki page is the one that helped me understand the basics of derivations. It explains how to package stuff without extra tooling.
stdenv.mkDerivationfrom nixpkgs adds a bunch of stuff, but the wiki linked doesn't explain it (yet?). You might find more information elsewhere.There's documentation for stdenv.mkDerivation and I apologize in advance for putting this evil upon you, but right now I don't have any other useful bookmarks. I learned it the hard way, but if you can contribute to the https://nixlang.wiki with what you learned, you could make it easier for the next person.
As for
nix-shell, once you've written yourdefault.nix, you can wrap it in ashell.nixand executenix-shellin the same directory.default.nixnix
{ pkgs ? import <nixpkgs> {} }: pkgs.stdenv.mkDerivation { pname = "chameleon"; version = "0.0.1"; # Update this to the real version of the package buildInputs = with pkgs; [ gnumake ]; # Add more necessary inputs here # While testing, your default.nix can reside in the checked out git repo src = ./.; # You can of course also start out like this straight away, up to you # Once testing is done, you can point this to a git repo pulled by nix # src = pkgs.fetchFromGitHub { # owner = "GideonWolfe"; # repo = "Chameleon"; # rev = "SOME GIT REVISION"; # hash = ""; # Start with an empty string and let nix complain with the real one, the use it # }; # There's a chance an install phase isn't necessary, but this is a skeleton # The contents are run in bash installPhase = '' runHook preInstall # Do non-standard installation stuff # See https://nixos.org/manual/nixpkgs/stable/#ssec-install-phase # for what is done by default runHook postInstall ''; }shell.nixnix
{ pkgs ? import <nixpkgs> {} }: let my-package = (import ./default.nix) { pkgs = pkgs; }; in pkgs.mkShell { inputsFrom = [ my-package ]; }Then you can run
nix-shelland see if your expected binary is inPATH. Once that is confirmed, you can add your package to yourconfiguration.nixnix
{ config, pkgs, ... }: { # The rest of your configuration.nix environment.systemPackages = with pkgs; [ # Import and call your derivation ((import /path/to/your/default.nix) { inherit pkgs; }) ]; }Hopefully that helped a little.
😂 It is not the best name, that's for sure. But I was hoping it would allow different technical decisions for example like getting off of github.
I wonder if the "aux" fork will continue to exist after that. However, if the forums continue to stay toxic, it wouldn't surprise me if another fork were made.
TL;DR the nix community forums are toxic from all sides
There's been a spout between core contributors + the foundation vs a loud portion of the community. Some related to code, but from what I've seen, the loudest have been about social issues and values.
It all boiled over when a military contractor wanted to join the list of sponsors for one of the conferences (upcoming on in USA?). That caused a lot of tension, the foundation came to a decision
notto accept sponsorship and tried to put sponsorship rules in place for future sponsors. These were however perceived as too blurry by some parts of the community as they wouldn't prevent such a situation from happening again.In the aftermath, a frequent contributor (John something?) was suspended and we're now here.
On top of everything an open letter was released targeting the creator of nix (Eelco Dolstra). They claim his benevolent dictatorship is not so benevolent and accuse him of multiple things.
There are people who just get on with writing code and are very helpful in the forums and other community channels, but the, let's call it "management style", of some people on the project is not beyond reproach. Big egos and a mix of bringing in issues external to the project has made the forums become a very unfun place to be.
Edited to clarify that they actually did accept sponsorship from the defense contractor.
Brb my morning NixOS update is failing to build (again).
When
nixos-rebuild switchsuddenly starts compiling GHC, firefox, CEF, or some other large package and you have to find the damn package that caused that rebuild. Always a good time.Another opinion about how it's OK for mega-corps to reap the benefits of opensource without contributing back and how we should just suck it up because of principles.
I understand he's a big contributor to ansible and other IaC, and most (all?) of his stuff is opensource. It's cool that he has the money to sustain himself and that he can stick to his principles with the money he has, but IMO either he lacks empathy or understanding for those in a place trying to make a living from opensource or in his opinion companies just can't be trusted with opensource if they have a CLA.
He's entitled to his opinions, but I don't share them.
Matrix clients are simple, easy, and nice to look at. The matrix server might need more resources, but it comes with everything out of the box. There's no need to fiddle with extensions and their weird naming, and hope that the other server/client also supports the extension. Also, are there bridges to other protocols?
I remember trying to get encryption working on Pidgin and it was all around a bad experience.
XMPP might be as powerful or more powerful than matrix, but nothing about it screams modern. It's like IRC for Gen X'ers.
- JumpDeleted
Permanently Deleted
That is what people sound like that have taken too many shrooms. Comes a bit too close to newage bullshit. "Life is the universe evolving to experience itself through you" and bullshit like that.
- JumpDeleted
Permanently Deleted
Hold on... how were you able to find out about his amazon browsing habits from a tracking code? I thought end-users wouldn't have that information but only amazon themselves (+ their 391712 friends).
flexbox made things so much easier, but still hard. There are just too many rules to keep in your head about
displayandpositionand how they affect other attributes. And the box model... wow. margin, border, padding, content, but he attribute isbox-sizingand it has border-box and content-box, but not the others.IINM it was written by people who came from print media (just like HTML) and that stuck.
I wish there were an alternative in a sane programming language that I could actually contribute to. For some reason PHP is extremely sparse in its logging and errors mostly only pop up on the frontend. Having to debug errors after an update and following some guide to edit a file in the live env that sets a debugging variable, puts the system in maintenance mode and stores additional state in the DB is scary.
Plus PHP is so friggin slow. Nextcloud takes noticeable time to load nearly anything. Even instances hosted by pros that only host nextcloud are just slow.
https://slint.dev/ has gotten there, IMO. They're working on a python binding and even to compile to android apps.
OK, what's the error?
Even with a QR code, it would be better to be able to take a picture of the logs to see what happened all the way until the kernel panic.
Anti Commercial-AI license