Buzzwords, marketingspeak, and/or other jargon
Posted Jun 10, 2005 14:43 UTC (Fri) by kevinbsmith
Parent article: A look at rpath Linux
It is so frustrating to read an "introduction" to a product or project, only to find that it was written for an audience that already knows what the product does and why someone might want to use it. It's sadly common among home pages of FLOSS projects, and conary falls into the same trap. After reading the article, and the linked introduction to conary, I *still* had very little idea what conary might offer over the other packaging systems that I have used: emerge and apt.
If I could offer one word of advice, it would be to include specific examples of real-world situations where existing tools do a poor job, and the new tool helps. The example in the article about abiword and enchant is a step in the right direction, but for those of us who have no idea what enchant is, or why it has 3 components, it just adds to the confusion.
Poking around on the conary wiki, I found this, which was more informative:
But based on that document, conary seems to mostly solve problems found in the RPM world. As a typical desktop user, it's still not clear to me how conary would be better than emerge or apt.
On a different topic, the description of the long-term goals of rpath sound similar to progeny's componentized Linux. It would be interesting to see a comparison between those two projects.
to post comments)