<samueldr>
(ah, didn't see you posted in #nixos too)
<init_6>
no any errors but not build at all
drakonis has quit [Quit: WeeChat 2.3]
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 258 seconds]
lassulus_ is now known as lassulus
srhb- has joined #nixos-dev
qyliss^work_ has joined #nixos-dev
pepesza has quit [Ping timeout: 250 seconds]
srhb has quit [Ping timeout: 246 seconds]
qyliss^work has quit [Ping timeout: 246 seconds]
ben has quit [Ping timeout: 246 seconds]
octe has quit [Ping timeout: 246 seconds]
rsa has quit [Ping timeout: 246 seconds]
Enzime has quit [Ping timeout: 246 seconds]
qyliss^work_ is now known as qyliss^work
octe has joined #nixos-dev
kgz has quit [Ping timeout: 258 seconds]
pepesza has joined #nixos-dev
LnL has quit [Ping timeout: 245 seconds]
kgz has joined #nixos-dev
janneke has quit [Quit: janneke quits Mes'sing]
janneke has joined #nixos-dev
init_6 has quit [Remote host closed the connection]
FRidh has joined #nixos-dev
init_6 has joined #nixos-dev
init_6 has quit [Ping timeout: 244 seconds]
emily has quit [Ping timeout: 264 seconds]
emily has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-dev
init_6 has joined #nixos-dev
Guest34980 has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-dev
<srhb->
https://github.com/NixOS/nixpkgs/pull/55723 breaks gcofborg eval of master (and maybe Hydra too) -- do we prefer a revert or removing the nxproxy name from all-packages?
<{^_^}>
#55723 (by jD91mZM2, 2 days ago, merged): x11docker: init at 5.4.1
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
init_6 has quit []
srhb- is now known as srhb
<srhb>
False alarm, simpler than I thought. It's only because it only exists as an alias and some callPackage depended on it. Fixed.
orivej has quit [Ping timeout: 250 seconds]
<Guest34980>
yeah, aliases shouldn't be referenced inside nixpkgs to make overrides work consistently IIRC
Guest34980 is now known as LnL
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 255 seconds]
orivej has joined #nixos-dev
init_6 has joined #nixos-dev
init_6 has quit []
MichaelRaskin has joined #nixos-dev
init_6 has joined #nixos-dev
init_6 has quit [Ping timeout: 272 seconds]
drakonis has joined #nixos-dev
<tilpner>
How opinionated is the manual? "here are the tools, do what you want", or "here are the tools, but please not try not using them"?
<tilpner>
(Context: wrapping AppImages instead of source builds)
<tilpner>
*please try not using them
<samueldr>
"prefer building from source"
<tilpner>
Hmm, I was looking for a docbook example of embedding shell command+output
<tilpner>
And I noticed there are markdown files too? Should I prefer writing docbook over markdown?
<emily>
don't be silly, nobody prefers writing docbook
<emily>
>_>
<tilpner>
But then how do I do the <warning> stuff in markdown?
<tilpner>
Maybe it just accepts that embedded
<emily>
I'm kidding, I think docbook is preferred for nixos documentation
<samueldr>
docbook please
<tilpner>
It seems odd to mix the two in the first place
<samueldr>
yeah, I don't know why there's a mix
<FRidh>
legacy and preference. There have been many discussions about it in the past and I think it's slowly now settling on docbook
FRidh has quit [Quit: Konversation terminated!]
<gchristensen>
tilpner: prefer docbook
<gchristensen>
the markdown integrates poorly and I rewrite it when I encounter it
<samueldr>
that extra CSS should be added to the build, imho
<gchristensen>
+1 samueldr
<gchristensen>
use <screen> tilpner
<tilpner>
Okay, I'll leave it in
<samueldr>
and someone (me) should do the touch-up work on the new visuals
<samueldr>
well, mostly the TOC thing
<gchristensen>
<3
<samueldr>
hey, with github actions, we might want to make a nixos-approved action for nix-build; if only for publicity reasons
<gchristensen>
oh cool
<samueldr>
it's stupidly easy, can be done without an "action", but AFAIUI an "action" could show up on the marketplace and be discoverable
<gchristensen>
I've been wishing for a nix-build -> s3 + cloudfront static site thing
<samueldr>
there's a google cloud thingy which I didn't look at, but I think it would basically allow the thing you say
<samueldr>
and I'm betting S3 is possible too
<gchristensen>
with actions?
<samueldr>
yeah
<gchristensen>
hmm!
<samueldr>
I need to confirm one bit of info, but I think e.g. cachix could be an action separate from nix-build
<samueldr>
so e.g. nix-build -> cachix
<gchristensen>
huh
<gchristensen>
I would very much like to have nix builds wrapped by firecrackervm or something for increased isolation, to allow for arbitrary builds without fearing too much for the host
<gchristensen>
I very much want to build things on *every* PR
<samueldr>
gchristensen: I think the only issue with your "push to master and nix-build to s3" is the lack of amazon actions
<samueldr>
though building your own "publish to s3" looks to be trivial enough :)
<samueldr>
imagine I had something like this ready and would want it published as something recognizable as nixos (e.g. the nixos org ideally), what's the next step?