The main problem with sudo and doas is that they are not developed by Lennart. Seriously.
fourwd
joined 6 months ago
It's working now
Try not to work in pitch darkness :)
Used dark (not black) themes everywhere for 8 years. My eyesight is still good according to my annual physical, but recently I've noticed that I have a hard time reading text written on a dark background. It is slightly blurred, especially when there is no light in the room.
Somewhere I still use dark themes, but I always try to switch to light mode if things look okay with code highlighting or smth.
If you build your app with glibc 2.32 and then run it with glibc 2.39, it will run fine. But it won't work the other way around.
There is no best README template, but for my personal projects I use this:
- Title
- Brief description of the project
- Features
- Build
- List of supported OS
- List of dependencies (what packages do I need to build your application)
- Commands to build the application (what do I need to do to build your application)
- Binary Locations (where can I find the built binary)
- Usage
- Program arguments (what do I need to provide to use your CLI application)
You can find an example here. I'm not saying this is the best README, but I think it's simple and informative.
Just build the app on very old distros like Ubuntu 16.04 if possible. But in general, packaging should be handled by the maintainer. If you want to be both a developer and maintainer, packaging problems will take up 75% of your time.
It's not really hard for us users to follow your README and just copy the built binary to ~/.local/bin.
It's very similar to FreeTube, which looks really cool.
This way we will have multiple sudo-tools on one system without the ability to remove all but one. Like now with all this crap like systemd-resolved, systemd-networkd, systemd-anothershitd and a bunch of tools that do the same thing, but are all required.