Bug 246144 - science/openkim: Update 1.1.1 -> 2.1.3
Summary: science/openkim: Update 1.1.1 -> 2.1.3
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Jason W. Bacon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-03 16:59 UTC by Yuri Victorovich
Modified: 2020-05-09 15:22 UTC (History)
0 users

See Also:
jwb: maintainer-feedback+


Attachments
patch (10.30 KB, patch)
2020-05-03 16:59 UTC, Yuri Victorovich
no flags Details | Diff
patch (10.34 KB, patch)
2020-05-03 17:02 UTC, Yuri Victorovich
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer 2020-05-03 16:59:32 UTC
Created attachment 214064 [details]
patch
Comment 1 Yuri Victorovich freebsd_committer 2020-05-03 17:02:09 UTC
Created attachment 214065 [details]
patch
Comment 2 Yuri Victorovich freebsd_committer 2020-05-03 17:19:43 UTC
Hi Jason,

There is also a duplicate port science/kim-api.

Additionally to the attached patch, I suggest to remove science/kim-api and to move science/openkim to science/kim-api. Repology shows that all other systems name this package kim-api, and tarballs are also named kim-api.


Thank you,
Yuri
Comment 3 Jason W. Bacon freebsd_committer 2020-05-09 15:22:29 UTC
This looks like a good plan.  You want to take care of it and assume maintainership?  I see you already own kim-api.  I had honestly forgotten that this port exists and no longer work with anyone who uses it.

Best,

  JB