jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
darfo has quit [Ping timeout: 248 seconds]
darfo has joined #crux-devel
farkuhar has quit [Quit: farkuhar]
groovy2shoes has quit [Ping timeout: 276 seconds]
groovy2shoes has joined #crux-devel
aardo has joined #crux-devel
ardo has quit [Ping timeout: 248 seconds]
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-devel
groovy2shoes has quit [Ping timeout: 276 seconds]
groovy2shoes has joined #crux-devel
farkuhar has joined #crux-devel
<beerman> I'm looking into making the mesa Pkgfile more complicated to accomadate the problem with vulkan driver dependencies.. I guess most people that don't specifically need these drivers don't want to install libclc just in case
darfo_ has joined #crux-devel
darfo has quit [Ping timeout: 248 seconds]
darfo has joined #crux-devel
darfo_ has quit [Ping timeout: 248 seconds]
<ukky> beerman: It would be nice not to install dependencies/components that are not required. For such ports complexity cannot be avoided.
<beerman> yep
<farkuhar> On MUSL-based CRUX, emmett1 bundled together llvm, clang, and compiler-rt into a single port (llvm-toolchain). Before I broke it up into separate ports, I relied on prt-get.aliases to avoid rebuilding what was already installed (during a depinst operation). Maybe mesa can be handled similarly.
<ukky> farkuhar: that was bad idea, to combine multiple independent packages into single port. I guess he was in a rush.
<beerman> heh, I did that a long time ago, ditched the idea quickly again
<farkuhar> VoidLinux has something similar, but the users don't need to know about it if they rely on binary packages. In the GitHub repo for void packages, you'll sometimes find a single build template that generates multiple binary packages.
<farkuhar> Example: llvm17 build template -> clang17, llvm17, and compiler-rt17 binary packages.
<farkuhar> texlive is another port that bundles together more components than would typically be used on any particular installation. One of these days I might sit down to list all the distfiles that the install-tl script actually fetches from upstream, for each choice of installation (minimal, medium, full), and then host a set of non-overlapping tarballs so that TeXlive users can install only the components they really need.
<beerman> sounds great
dlcusa has quit [Ping timeout: 258 seconds]