Matthias-Christian Ott [2007-10-06 12:26]:
Footprint mismatches occur, because the user has other software installed than the developer who generated the footprint. Configure (autotools) enables additionally features and additionally files are installed. Thus the footprint mismatches. Isolated builds and feature flags (~ USE flags) prevent this situation.
You're talking about how pkgutils6 violetes Per's vision and the CRUX philosophy etc, and yet here you are saying we need a better ports/pkgfile system. It's all backwards!
I do not see why C++ would have been so essential to the spirit of CRUX: there is no precise design or aim behind that choice, and the advantages of C over C++ are, I would say, well known.
Yes, but including standard algorithm source code (lists, binary search trees) conflicts (in my opinion) with the design philosophy of CRUX.
Well, the current CRUX maintainers believe otherwise it seems. And all of us are long time users and contributors, so I believe we do know better about what fits with CRUX' philosophy, and Per's ideas of this distribution than you.
architecture. Why should CRUX restrict their usage to i686?
Because it's the most widespread architecture in use in typical desktop and server systems today. eg I only have i686 boxes, how the hell can I vouch for my ported software if I cannot even test it on x86-64? On the one hand, you're constantly claiming that we'd violate CRUX philosophy, on the other hand you're suggesting to extend the ports system etc in ways that were never meant to be. You're wrong. Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?