<bountyht>
Well it does not look like the worst deal
<bountyht>
I gotta go. See you later
<SiFuh>
Later
jue has quit [Quit: leaving]
tse has quit [Changing host]
tse has joined #crux
Stealth has quit [Quit: Dont wait to die to find paradise...]
DaViruz has quit [Ping timeout: 265 seconds]
Stealth has joined #crux
DaViruz has joined #crux
humky has joined #crux
Moth has joined #crux
<bountyht>
SiFuh: I am back. Being forced to install Windows on somebody else's computer
<bountyht>
SiFuh: Paranoid question: Why should I trust your updated iso?
<dbrooke>
even though unofficial the updated ISOs are maintained by https://crux.nu/Profiles/MattHoush so they should be as trustworthy as the official ones
<bountyht>
That is what I wanted to hear
<bountyht>
HOw deep is MattHoush in the development team?
<pedja>
he's been around since almost the beginning :)
<bountyht>
Good to know :-P
<bountyht>
Sounds like what Eric Hamelees is to Slackware
<elderK>
Guys, is there a better way to find out what dependencies a package has rather than going through its CMakeLists / configure scripts?
<elderK>
I wish there was a comprehensive way to say "Yo, gimmie all your dependencies, all of them!"
<elderK>
Sure, I might be able to build some program, but that doesn't mean I have the full feature set. And sometimes they don't document their deps on the github or README.
<elderK>
:(
Moth has quit [Remote host closed the connection]
Moth has joined #crux
<elderK>
I guess the only real good way is to have a VM or chroot that has a "bare" Crux install and make my packages in there.