Jump to content
  • 0
digifuzzy

How to handle CatPkg new versioning scheme

Question

media-gfx/plantuml is java-based software that enables text-based UML diagram generation (similar in nature to graphviz but focused on UML).

Latest available in tree is version 8046 (or July 2016). Newer versions(v1.2019.9) are available and tweaking ebuild to build this package with latest software works well.

However, portage becomes an issue. Using the newer ebuild as plantuml-1.2019.1 looks to portage as a "downgrade". Short-term fix is to mask package earlier versions (i.e. >=media-gfx/plantuml-8046).

How to best to handle definitively change in versioning scheme?

Share this post


Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0
14 hours ago, bcowan said:

We used to let portage handle these moves transparently using profiles/updates. I don't know if that's still the case.

Doing an emerge of a package marked "8046" to "1.2019.9" is seen by emerge as a downgrade. I wasn't sure of the "practical", "portage" way to handle or otherwise convince portage to ignore of consider a revision regex pattern to be less than current. I had to throw the question out to the studio audience.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...