Why Are Hplip And Hpijs Always So Back Dated?

Home » CentOS » Why Are Hplip And Hpijs Always So Back Dated?
CentOS 1 Comment

My fully patched CentOS 6.5 system uses:

My wife’s printer becomes supported at 3.13.somethingOrOther and the current release is 3.14.something.

Why are we so far behind?

I realize that I can download the latest, uninstall the RPM versions and compile and build and install the source copy. If I was going to follow that route, I would prefer to build an rpm and install it normally. I have been looking on the Internet and not found anything to turn the release from HP into a binary RPM.
(That does not mean it is not there.)

I know it must be doable since there are rpm’s in the repositories. My skill with RPM’s is somewhat limited, but does anyone know of a set of instructions and a spec file that could be used to get started on this process?

Thanks in Advance

Bob, Phoenix, AZ,

One thought on - Why Are Hplip And Hpijs Always So Back Dated?

  • I’ve never tried it with hplip, but many rpms can be updated by simply downloading and installing the srpm for the version that you’re trying to update from, putting the newer source file into rpmbuild/SOURCES, updating the spec file in rpmbuild/SPECS, and then typing: rpmbuild -ba myfile.spec

    The source rpm will have a spec file included.