content/add-to-config: recommend nixpkgs for stable versions #58

Merged
jade merged 1 commit from new-mechanism into main 2025-08-26 02:28:52 +00:00
Owner

This also updates all our modules which are now passthru to nixpkgs by
default.

Signed-off-by: Raito Bezarius raito@lix.systems

This also updates all our modules which are now passthru to nixpkgs by default. Signed-off-by: Raito Bezarius <raito@lix.systems>
This also updates all our modules which are now passthru to nixpkgs by
default.

Signed-off-by: Raito Bezarius <raito@lix.systems>
@ -25,0 +21,4 @@
- Uses up-to-date system dependencies, e.g. latest glibc, OpenSSL, AWS SDK.
- Is cached by `cache.nixos.org`, no local builds are required
- Consistent compatibility with advanced features of Nixpkgs: cross compilation or static builds.
- Using the Lix NixOS module (recommended for bleeding edge versions):
Owner

if we mean main it should link to the running main instructions.

if we mean main it should link to the running main instructions.
Author
Owner

right

right
raito marked this conversation as resolved
@ -25,1 +23,4 @@
- Consistent compatibility with advanced features of Nixpkgs: cross compilation or static builds.
- Using the Lix NixOS module (recommended for bleeding edge versions):
- Fresh version of Lix right out of the freezer
- Ships with slightly older system dependencies, e.g. glibc, OpenSSL.
Owner

this isn't true? it's always built using the user's nixpkgs. the only way this isn't true is on non NixOS where it's our bins

this isn't true? it's always built using the user's nixpkgs. the only way this isn't true is on non NixOS where it's our bins
Author
Owner

this is true only if you harness the power of follows which very few can?

this is true only if you harness the power of `follows` which very few can?
Author
Owner

hm actually we are always doing an overlay i guess and i consistently get that wrong

hm actually we are always doing an overlay i guess and i consistently get that wrong
raito marked this conversation as resolved
@ -55,3 +65,3 @@
```
# Using the Lix NixOS module
## Advanced change
Owner

HA HA HA YES

HA HA HA YES
raito marked this conversation as resolved
@ -58,0 +73,4 @@
```nix
{ pkgs, ... }:
{
nixpkgs.overlays = [ (self: super: {
Owner

maybe want to introduce a variable so you have the selected version in one spot

maybe want to introduce a variable so you have the selected version in one spot
Author
Owner

i considered that but i wanted to keep it simple

i considered that but i wanted to keep it simple
raito marked this conversation as resolved
@ -58,0 +80,4 @@
nix-eval-jobs
nix-fast-build
colmena;
}) ];
Owner

do we want to mention that setting nix = pkgs.lix works? because it is supposed to, but i definitely think this way of using stuff we explicitly override is probably safer.

do we want to mention that setting `nix = pkgs.lix` works? because it is *supposed to*, but i definitely think this way of using stuff we explicitly override is probably safer.
Author
Owner

i believe not, this is a too simplistic endpoint and i don't want people to learn it unnecessarily

i believe not, this is a too simplistic endpoint and i don't want people to learn it unnecessarily
raito marked this conversation as resolved
@ -58,0 +114,4 @@
# Using the Lix NixOS module (recommended only for bleeding edge builds)
_Thank you for considering Lix bleeding edge, this helps us a lot to make Lix better._
Owner

is this referring to main? merely .latest?

is this referring to main? merely .latest?
Author
Owner

main

main
raito marked this conversation as resolved
@ -63,2 +123,4 @@
perfect time to get up, get some water, and stretch for a bit.
This only makes sense if you care about **bleeding edge builds** and you are fine
with **losing the cache** advantage of using nixpkgs.
Owner

we should be clear about what bleeding edge means. bleeding edge implies it's not received QA but this is probably not that? it's probably just-released versions right?

we should be clear about what bleeding edge means. bleeding edge implies it's not received QA but this is probably not that? it's probably just-released versions right?
Author
Owner

it means main

it means main
raito marked this conversation as resolved
raito force-pushed new-mechanism from 574313267b to 7acce1a23a 2025-08-25 22:22:31 +00:00 Compare
raito force-pushed new-mechanism from 7acce1a23a to 83ab07d76b 2025-08-25 22:24:02 +00:00 Compare
jade left a comment
Owner

beautiful. one small language usage problem.

beautiful. one small language usage problem.
@ -25,0 +20,4 @@
- Official, supported builds maintained by the `nixpkgs` contributors and the Lix team
- Is cached by `cache.nixos.org`, no local builds are required
- Consistent compatibility with advanced features of Nixpkgs: cross compilation or static builds.
- Using the Lix NixOS module, [recommended uniquely if you run main](https://wiki.lix.systems/books/lix-contributors/page/running-lix-main)
Owner

en anglais on devrait probablement dire "only recommended if you run Lix main". "uniquely" n'a pas la bonne sens ici.

en anglais on devrait probablement dire "only recommended if you run Lix main". "uniquely" n'a pas la bonne sens ici.
Author
Owner

merci beaucoup

merci beaucoup
raito marked this conversation as resolved
@ -70,2 +72,3 @@
{ pkgs, ... }:
{
inputs = {
nixpkgs.overlays = [ (self: super: {
Owner

pedantry which you can ignore: maybe use final, prev.

pedantry which you can ignore: maybe use final, prev.
raito marked this conversation as resolved
@ -160,2 +96,3 @@
great time to check out some of the [community's resources on Nix](/resources).
---
To use a different version of Lix, replace `stable` with `latest`, `git`, or a specific version like `lix_2_93`.
Owner

we might actually want to obliterate this entire non-flakes section because it's now exactly the same (HA HA HA YESSSSS), but i can't quite read this diff at the moment, so it's probably better to do in a separate PR.

we might actually want to obliterate this entire non-flakes section because it's now exactly the same (HA HA HA YESSSSS), but i can't quite read this diff at the moment, so it's probably better to do in a separate PR.
Author
Owner

It's already obliterated AFAIK?

It's already obliterated AFAIK?
raito force-pushed new-mechanism from 83ab07d76b to 1579252c23 2025-08-26 02:21:29 +00:00 Compare
jade merged commit 023784dedb into main 2025-08-26 02:28:52 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix-website#58
No description provided.