4 ms·
Hmm. He might rail against /usr/ports/ but it was better than the alternatives of the time (I note pkgsrc, maybe comparable, certainly similar) His beef is tha
by ggm 3y ago
Hmm. He might rail against /usr/ports/ but it was better than the alternatives of the time (I note pkgsrc, maybe comparable, certainly similar)
His beef is that people are lazy. If there is a perl tool to munge something you use it, even if the rest of the process uses Python. This is the reductionism of
"if you start in awk stay in awk" which is good, honest and .. hard.
Ports is better than APT. apt, has the disease of 'I made a bundle for you but the name is not indicative of whats in it' -where Ports has metaports which are explicit what they pull in to make the "thing" they meta over.
APT has the "-dev" norm now. thats ok, but sort of stupid too. How can it possibly make sense to have to pull in the -dev thing to use its shared libs standalone in another package? (I have seen this)
Ports is the bazaar but with sub-zones. Like the Grand Bazaar in Istanbul, things tend to clump together. Sometimes you wonder why its in sysadmin/ and not text/ but in the end its birds-of-a-feather.
Homebrew ditched M4 for Ruby. Gak.
CPAN is the enemy.