Don't Use Epoch

RPM Add comments

Epoch is the “our company in incapable of managing a version” admission; it’s the single most evil thing added to RPM, only to address a vendor’s internal issues with version numbers that always increase. With an actual plan for version numbers, epoch is never necessary. Now that it’s there, it’s a bonehead “easy way out” of having to solve a problem.

How logical is this:

$ sudo rpm -Uvh /home/repos/kludge/doxygen-1.6.0-1.i386.rpm
Preparing... ########################################### [100%]
package doxygen-1.4.7-1.1.i386 (which is newer than doxygen-1.6.0-1.i386) is already installed

Version 1.4.7 newer than version 1.6.0? It’s not logical. I’m assuming it’s because of Epoch, but Epoch data doesn’t show. Epoch is hidden, secret, and causes confusion like the confusion above.

…and really, once an epoch is set, it’s too easy just to bump it up, and that causes a complete scramble in the orderly, logical increase of version numbers.

The only way to cripple this is to choose the highest epoch number possible. That’s why my Epochs are maxint.

Leave a Reply

WP Theme & Icons by N.Design Studio
Entries RSS Comments RSS Log in