Yeah, but if there is some software package I like, I'm more
inclined
to install it from source rather than to screw around with rpms... Be
that finding a prebuilt one that's six months out of date or going through
the extra bother to generate rpms.
I've built rpms before, but the question I'd have then is what would be
expected of me if I ~were~ to maintain a package myself. It's easy for me
to test on AMD64 and (possibly) x86, but I'm not going to be able to
support a package for the Itanic.
That's not expected. Maintainers are expected to:
- keep the package building on whatever they can and solicit help from
people running on minority platforms for testing
- monitor the software for updates and security issues
- stay current with the expected and intended use for the package
- keep abreast of licensing issues with the package.
- keep the packaging guidelines applied and cleanly implemented in the
package.
-sv