Bug 231844 - devel/hwloc: Update to 2.x or create devel/hwloc2 (if appropriate)
Summary: devel/hwloc: Update to 2.x or create devel/hwloc2 (if appropriate)
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL: https://www.open-mpi.org/projects/hwl...
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2018-10-01 08:47 UTC by O. Hartmann
Modified: 2019-04-14 06:45 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (phd_kimberlite)


Attachments
shell archive of a new port (19.97 KB, text/plain)
2018-10-01 14:13 UTC, Eijiro Shibusawa
no flags Details
Diff file to update to 2.0.3 (13.59 KB, text/plain)
2019-01-14 07:41 UTC, wen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description O. Hartmann 2018-10-01 08:47:50 UTC
HWLOC 2 is out and it would be nice to have either devel/hwloc (which is version 1) updated to 2 or having an additional port, devel/hwloc2.

Thanks in advance.
Comment 1 Eijiro Shibusawa 2018-10-01 14:13:01 UTC
Created attachment 197676 [details]
shell archive of a new port

Please try the attached port.
NOTE:
- This port was tested with portlint 2.18.3 / poudriere
- Please refer the release announcement.
https://github.com/open-mpi/hwloc/blob/v2.0/NEWS
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2018-10-15 09:58:58 UTC
Might be worth getting an inventory of existing ports that depend on devel/hwlock (1.x) to determine their compatibility status/readiness for 2.x, in order to better ascertain the need for two seperate ports, and/or potential port upgrade paths

lang/pocl is 2.x compatible: https://github.com/pocl/pocl/issues/358
Comment 3 wen 2019-01-14 07:41:48 UTC
Created attachment 201113 [details]
Diff file to update to 2.0.3

I create a diff file and ask for a exp-run.
Comment 4 Kubilay Kocak freebsd_committer freebsd_triage 2019-04-14 06:45:06 UTC
Superseded by bug 231844