lavaball has quit [Remote host closed the connection]
<cruxbot>
[contrib/3.8]: [notify] nginx: updated to version 1.29.1; security update, fixes CVE-2025-53859
<cruxbot>
[opt/3.8]: libsass: moved from contrib
<cruxbot>
[contrib/3.8]: libsass: moved to opt
tsundokuboi has joined #crux
tsundokuboi has quit [Client Quit]
tsundokuboi has joined #crux
ppetrov^ has joined #crux
tsundokuboi has quit [Ping timeout: 260 seconds]
tsundokuboi has joined #crux
tsundokuboi has quit [Ping timeout: 260 seconds]
tsundokuboi has joined #crux
tsundokuboi has quit [Ping timeout: 260 seconds]
tsundokuboi has joined #crux
tsundokuboi has quit [Ping timeout: 260 seconds]
tsundokuboi has joined #crux
bleb has quit [Server closed connection]
bleb has joined #crux
tsundokuboi has quit [Ping timeout: 260 seconds]
tsundokuboi has joined #crux
tsundokuboi has quit [Ping timeout: 260 seconds]
lavaball has joined #crux
GazL has joined #crux
tsundokuboi has joined #crux
<GazL>
Morning all.
<GazL>
Quick question for those of you who make modifications to stock pkgbuilds regarding workflow: Do you prefer a separate repo to act as an overlay, or do you create a custom branch in a local clone of CRUX's git repo?
shahab has quit [Ping timeout: 276 seconds]
tsundokuboi has quit [Ping timeout: 260 seconds]
lavaball has quit [Remote host closed the connection]
shahab has joined #crux
<jaeger>
I keep an overlay directory, very simple
<cruxbot>
[contrib/3.8]: go: updated to version 1.25.0
<cruxbot>
[contrib/3.8]: docker-compose: updated to version 2.39.2
<cruxbot>
[contrib/3.8]: docker: updated to version 28.3.3
<cruxbot>
[contrib/3.8]: containerd: updated to version 2.1.4
<GazL>
jaeger: that's what I did through 3.7's lifetime. Only problem I found with that approach is that the overlay repo can hide upstream version updates.
<GazL>
Using git, I can merge any updates CRUX provide using a git merge, though it is more involved.
<GazL>
... but it's still early days, it might become to much of a PITA as time goes on ;)
<farkuhar>
GazL: Set yourself a cronjob that runs `prt-get dup -vv` periodically, and it will alert you when something in your overlay is masking a higher version in another repo.
shahab has quit [Quit: Out!]
<GazL>
farkuhar: yes, used to do prt-get dup regularly during 3.7 when I had an overlay repo. I was just curious if anyone was using a git branch, but seems like 'overlay' is the common approach if you two are representative.
<jaeger>
You certainly can use a git branch if you want to
<jaeger>
'17 ways to solve a problem' is the unix/linux way :D