| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
since i am apparently now fingerable at plan.cat, might as well have the
utility for it (… though has there ever been a more egregious case of
"just using nc is simpler anyways"?)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
this does a lot of things, most of which are maintenance:
- sources update
- adjust newly-renamed options
- swap some packages that were removed / renamed
- update nomsring to newer default ghc
- remove the deprecated lib.mdDoc from modules/*.nix
- disable the nixpkgs mollysocket module so my own keeps evaluating
- bundle the package definition of hikari & wlroots 0.15, which nixpkgs
has removed as unmaintained (in fairness, they are unmaintained)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this is, in the widest possible sense, a revert of
e88fed18f499a3e8ac98c772bbb62f00d1f8d1d7, which was now a little over
two years ago.
Of course, lots of things have changed since then:
- this uses npins instead of niv, which is both simpler and still
maintained
- i haven't brought back the old deploy lib; I still use
deploy-rs (with some modifications) to deploy things
- if you actually use my stuff downstream, you can now use packages/ &
tests/ & modules/ as entry points directly, while still having some
control over inputs
- (since i also don't believe any downstream users actually exist, i've
not bothered to have a shim flake.nix so your stuff probably just
broke. well, it was an experimental feature, anyways)
- in general there's a lot more of the old-fashioned structure back
again, with default.nix files in subdirectories that form a
structure, not like how almost everything was just imported in the
one big flake.nix file
For people who are interested in also having a non-flake config similar
to this one, it's probably best to take a look at inputs.nix (and also
at npins, of course)
|
| |
|
|
|
| |
lowdown isn't very good, but at least it doesn't have any weird cloud
features (why is this the standard for things that show text??)
|
| | |
|
| |
|
|
|
|
|
| |
doggo is more maintained, can use IPv6, queries all nameservers at once
by default, and generally feels comfier.
(now if only it had a man page ..)
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
why am i still building it myself all the time?
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
(mostly to reduce hassle / build times for smaller machines)
|
