3 ms·
My packaging experience is limited, but I found the docs were quite poor. It took perseverance & researching install error messages to create an RPM that worked
by mch82 3y ago
My packaging experience is limited, but I found the docs were quite poor. It took perseverance & researching install error messages to create an RPM that worked. So you might consider hiring for people willing to do that kind of work.
The good news is that I learned a tremendous amount about where programs and files should actually be installed through packaging. It was surprising to me how many conventions package managers enforce. I was also surprised how poorly software followed those conventions when installed without package managers. Packaging improves user experience, developer experience, and quality. Can’t recommend it enough!
- pxc 3y ago> It took perseverance & researching install error messages to create an RPM that worked. So you might consider hiring for people willing to do that kind of work. At its toughest, packaging is a long series of exchanges: one build error for another. It is a stubborn, patient, rabbithole diving, well-I'll-be-damned, yak-be-shorn kind of work. > The good news is that I learned a tremendous amount[.] [...] Can’t recommend it enough! And it's totally worth it, both for the packager and their users. :D