3 ms·
Congratulations! You are now closer to being Enlightened. You now have a closer understanding pf the hundreds of thousands of man-hours that distribution maint
by peterwwillis 12y ago
Congratulations! You are now closer to being Enlightened.
You now have a closer understanding pf the hundreds of thousands of man-hours that distribution maintainers spend doing this every single day just to give you a working application. Keep in mind of course that all of which you performed will not replicate properly, because it doesn't use a spec file, doesn't record its build deps, run deps, permissions, has no uninstall or upgrade, doesn't use standard paths, probably skips a whole bunch of correct procedure and bug fixes, uses some real-time dynamic package managing/installing thingie, yadda yadda....
It's not that software development procedures are broken; actually, they're really, really well defined for most of the Open Source world. It's just that most humans have no clue how much work goes into giving them some 'basic' products. Kind of like how most people have no idea how much of a multinational effort goes into producing a bottle of Coke.
Could said tool be written with no dependencies? Sure. But that would be a total nightmare in and of itself. At the end of the day, code reuse and layers of abstraction are useful... as long as they're designed and used properly.
- VLM 12y agoThe funny thing is that given maintainers do this all the time so they'll work faster, and he's apparently figuring it all out the hard way the first time, by the time he's done the maintainers have likely already uploaded. Probably. Or at least they could have.
- peterwwillis 12y agoIt's usually not that simple. If you already have passed the learning curve of knowing intimately how to maintain packages for your distro, it's a "simple" matter of updating the old .spec files with the newer versions and sending the distro maintainers your newer .spec. But there's no guarantee they'll incorporate your new package in a timely manner (and it will go into an -UNSTABLE tree anyway, which his Centos 6 install isn't using)
- krakensden 12y agoHe is also studiously ignoring the work of the RPM packagers, which is making everything worse.