RFE: More verbose `port outdated` when epoch is incremented but version and revision are left unchanged

[lperry (Perry Lee)]

port outdated's output can be a little confusing when the epoch is incremented but the version and revision are kept the same. For example:

openssl                        0.9.8k_0 < 0.9.8k_0

I've attached a patch that (1) sets the flag field and (2) additionally displays the epochs when the above situation occurs. For example:

foobar                         0.1_0_0 < 0.1_0_5        E

[jmroot (Joshua Root)]

I don't like displaying the epoch on the right, it makes it look less significant than the revision.

[lperry (Perry Lee)]

That's a good point; though, as another thought, should the epoch even be displayed?

From my perspective, users are only concerned with the upstream version; in the case that a port's version/revision is kept the same or decremented, I think it would be enough to just set the flag to E.

I've updated the patch to just set the flag to E whenever the epoch is incremented - not only when the installed_version matches the latest_version. For example, 0.1_0 < 0.0_0 E .

[lperry (Perry Lee)]

Updated on 04/09

[raimue (Rainer Müller)]

I like the "E" flag. The actual epoch values don't matter, it is only important to understand why a downgrade is considered outdated.

[jmroot (Joshua Root)]

r64960