<ukky>
pkg_installed creates links at /usr/ports/installed/. These links are not used by any other prt-utils tool. What is the purpose of those links? ISO packaging? Cross-compiling?
<jaeger>
No idea there, never had any use for it myself
<ukky>
My only conclusion of a use case for it would be to quickly track installed packages from a specific repository, for example: ls -l /usr/ports/installed/ | grep '/usr/ports/opt/'
<jaeger>
maybe so
<farkuhar>
ukky: your exchange with lavaball yesterday reveals another use case ("why can't i just compile everything and no binaries?") After installing from the ISO, lavaball would be able to 'cd /usr/ports/installed && pkgmk -fr -u --recursive'
<farkuhar>
something to remember about these prt-utils scripts: most of them were written while prt-get was still under active development (2004--2008). It wasn't obvious at the time which features would eventually land in prt-get, so the prt-utils authors satisfied the demand for new features by writing scripts in bash or perl, rather than forking the prt-get codebase and submitting pull requests to jw.
jubalh has joined #crux
jubalh has left #crux [#crux]
<ukky>
farkuhar: You are right. Running 'pkg_installed' creates symlinks, but if symlinks are not required, then 'prt-get listinst' gives the same result
<farkuhar>
ukky: the May 2008 mailing list archives illustrate the then-dominant idiom for taking into account the installed packages. You would more often see 'pkginfo -i | grep foo' in a Pkgfile, not 'prt-get isinst foo'. The latter only became common once the prt-get feature set had stabilized to the same extent as the pkginfo feature set.
dim44 has joined #crux
<jaeger>
and maybe importantly after prt-get became part of core
<dim44>
Hello friends. I know it's a long shot but is anyone doing blockchain development and more particularly, using dfx from icp. I'm having a difficult to troubleshoot problem that persists even in virtualized guest systems, thinking it's got something to do with my kernel.
<ukky>
What was the 'old' way (pre prt-get era) to rebuild a port? Now it is 'prt-get update --fr foo'. Was it 'cd /usr/ports/repo/foo && pkgmk -f && pkgadd foo.tar.gz'?
<jaeger>
probably 'pkgmk -d -f -u' I'd guess
<jaeger>
but either would work
<ukky>
And waht was the original sequence of commands to install new package with all dependencies? Would 'pkgmk -r foo' build/install dependencies too?
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux
<farkuhar>
ukky: there was no automatic dependency resolution until prt-get. Users would keep track of dependencies manually. Before prt-get became canonical, there wasn't even a consensus on how to list a port's dependencies in the Pkgfile!
<ukky>
life would be tough without 'prt-get depends' and 'prt-get dependent'
Romster has quit [Ping timeout: 255 seconds]
Romster has joined #crux
ppetrov^ has quit [Quit: Leaving]
groovy2shoes has quit [Remote host closed the connection]