<dlcusa>
BTW, can't prt-get lock glibc--package not found.
<dlcusa>
same for libxcrypt, unsurprisingly.
_whitelogger has joined #crux-musl
_whitelogger has joined #crux-musl
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-musl
<dlcusa>
It seems to me enhancing prt-get's --ignore parameter to support a permanent list of such personna-non-grata packages will be needed long term for non-glibc distros.
<farkuhar>
dlcusa: What happens if you manually add the names of the unwanted packages to /var/lib/pkg/prt-get.locker?
<dlcusa>
Haven't tried it--will get back to you in some value of soon.
<farkuhar>
I know you already reported "package not found" when trying `prt-get lock glibc` but that behaviour is just prt-get trying to sanity-check its arguments. Bypassing the test of whether the package is actually installed would have appended glibc to the lock file, no questions asked.
SiFuh_ has quit [Remote host closed the connection]
SiFuh_ has joined #crux-musl
<emmett1>
dlcusa: afaik, 'prt-get lock' only works for installed ports
<emmett1>
so in this case, you need to add 'glibc' to /etc/prt-get.aliases
<emmett1>
make it alias to musl
<emmett1>
'musl: glibc libxcrypt'
<emmett1>
this way glibc and libxcrypt wont get pulled anymore
<emmett1>
btw dlcusa, it seems i forgot to add my musl repo git file to /etc/ports in my CRUX-MUSL ISO
<farkuhar>
emmett1: I don't have linux-pam installed, but `prt-get listlocked` does report linux-pam. Either I manually edited /var/lib/pkg/prt-get.locker, or I used a variant of prt-get that doesn't sanity-check the arguments of a 'lock' operation.
<emmett1>
farkuhar: have you installed linux-pam previously and 'prt-get lock' it, then removed it again?
<farkuhar>
emmett1: nope, never had linux-pam installed on this machine.
<emmett1>
i do not tried other prt-get variant except from original CRUX
<emmett1>
hmm..then not sure why is that
<farkuhar>
I'm thinking it might be a good idea to pre-populate $PKG/var/lib/pkg/prt-get.locker with glibc and libxcrypt, for the prt-get port in our MUSL overlay. Either that, or pre-populate $PKG/etc/prt-get.aliases with the line you suggested.
<emmett1>
yes, since theres port outside core repo defined glibc as dependency, so this pre-populate should be done
<emmett1>
either way should fine
<emmett1>
as long it will not pull glibc
<farkuhar>
emmett1: My git repo for prt-get has several branches, representing different features that have been requested over the years. One of these branches deals with optional dependencies, another branch implements a mixed install/update mode, and another branch implements a `sync` command (alternative to `ports -u`).
<farkuhar>
I also have a Perl-based rewrite, which I suspect is the one that doesn't sanity-check the arguments to a `lock` command.
<farkuhar>
As far as I can recall, in the C++ version I never removed the test of whether the arguments to a `lock` command were installed, even though such a relaxed interpretation would be useful in preventing glibc and libxcrypt from getting swept up in a depinst transaction.
<emmett1>
farkuhar: great, one of those thould be used in OpenCRUX.
<emmett1>
I never look at prt-get source code how it should work, but I was having bad time back then when writing bootstrap script for my CRUX-MUSL iso, glibc keeps get pulled, until i figured out i need to alias it to musl (or any installed packages) to prevent it get pulled