farkuhar has quit [Remote host closed the connection]
humky has quit [Remote host closed the connection]
humky has joined #crux
humky has quit [Quit: Leaving]
humky has joined #crux
<r0ni>
if anyone would/could post a package of qt6-webengine-6.7.0 I'd be eternally grateful...
brian|lfs has joined #crux
<remiliascarlet>
I'd be more grateful if web developers would stop relying on a gazillion different Javascript frameworks and an even bigger amount of NPM packages so that the whole Chromium engine wouldn't need to be so goddamn bloated in the first place.
<remiliascarlet>
Probably not gonna happen until something even more bloated comes out.
serpente has quit [Ping timeout: 268 seconds]
DesRoin has quit [Ping timeout: 268 seconds]
DesRoin has joined #crux
groovy2shoes has quit [Ping timeout: 260 seconds]
groovy2shoes has joined #crux
pfr has joined #crux
pfr has quit [Client Quit]
pfr has joined #crux
pfr has quit [Quit: Quit]
zorz has quit [Quit: leaving]
pfr has joined #crux
pfr has quit [Client Quit]
ukky has quit [Ping timeout: 252 seconds]
lavaball has joined #crux
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
tarxvfz has joined #crux
ppetrov^ has joined #crux
nekobit has quit [Ping timeout: 268 seconds]
iNomad has joined #crux
chrcav has quit [Ping timeout: 260 seconds]
chrcav has joined #crux
chrcav has quit [Ping timeout: 268 seconds]
iNomad has quit [Ping timeout: 260 seconds]
iNomad has joined #crux
humky has quit [Quit: Leaving]
humky has joined #crux
farkuhar has joined #crux
<tarxvfz>
Hi All! I am a crux newbie, somwhere on the learning curve after handbook/installation/faqs.
<tarxvfz>
My question is: how can I make a local ports collection on my filesystem only: for example /usr/ports/local ? What do I need for this?
<tarxvfz>
s/kicstart/kickstart/
<tarxvfz>
some quick "kicstart", or pointer to some documentation, even pointer to man pages would be apreciated
<farkuhar>
tarxvfz: Modifying an existing port is often easier than creating your first port from scratch. Just create a directory for your collection (/usr/ports/local as you wrote), and copy an existing port there. Make your changes, activate the repo in /etc/prt-get.conf (earlier than the repo you copied it from), and voila: you have a local ports collection!
<tarxvfz>
ok, 10x, farkuhar! what bugs me - how to arrange some signing keys in /etc/ports/local{pub,priv} ? and how to sign the .signature file. I suceed until now with .md5sum files, but I read that .md5 will be appreciated soon
<tarxvfz>
s/appreciated/DEpreciated/
<farkuhar>
Signing keys are only relevant if you want to publish your ports for the benefit of other CRUX users. But if you want to use them from the very beginning, see here: https://crux.nu/Wiki/SignedPorts
<tarxvfz>
many thanks! that is what I need :)
<farkuhar>
Masking ports from the official repositories with your personal overlay is the canonical way to deal with core ports that are not configured to your liking (e.g., shadow or openssh which depend on linux-pam). But a personal overlay requires manual updates. You can automate the patching of official ports as part of the 'ports -u' routine; see Erich Eckner's post to the mailing list for one method (since modified by ukky).
<tarxvfz>
farkuhar: generally - you read my mind :) my quest with crux started by reading some conversations in #crux group... and after the learning curve... I probably will try to "mask" the linux-pam and definitely ssh :) thank you for the clarifications
<farkuhar>
tarxvfz: no problem! glad to help :-)
tarxvfz has quit [Ping timeout: 260 seconds]
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]