News for hackers. Stuff that matters.
Re:Argh-P-M – Dissecting the RPM file format (2016) by notacoward on Wednesday July 11, 2018 @09:42AM (#17506746)
Yes, the RPM format is crappy. A normal person would have seen that quickly (or known it already), gotten their business done, and moved on. What's the point of dissecting every little piece to criticize, or of criticizing even the oversights or practices normal for their time as much as the things that are truly insane? It's just rage-bait.
Re:Argh-P-M – Dissecting the RPM file format (2016) by fuzzy2 on Wednesday July 11, 2018 @10:51AM (#17507379)
To learn from past mistakes, probably. If you want to create something better, you first need to determine what’s bad.
Re:Argh-P-M – Dissecting the RPM file format (2016) by yjftsjthsd-h on Wednesday July 11, 2018 @11:21AM (#17507599)
You also need to understand how it got that way. In this case, a lot of the things the author takes issue with are a combination of eternal backwards compatibility, really wide portability, and having originally been devised when memory was tiny and processors were slow. It's one of those things where if you rebuilt it yourself, by the time you covered all features of the original, you would be just as ugly.
Re:Argh-P-M – Dissecting the RPM file format (2016) by cesarb on Wednesday July 11, 2018 @11:38AM (#17507748)
I agree. For instance, one of the things the author complains about is the rpmlib(...) dependencies. To me, they are clearly a way to make older versions of rpm (which do not know anything about these features) fail cleanly with a "missing dependency" error.
Re:Argh-P-M – Dissecting the RPM file format (2016) by rsynnott on Wednesday July 11, 2018 @11:22AM (#17507605)
For the benefit of the next person who has to figure this out, with bonus angry commentary?