Re: Any interest in ROCm packaging?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I maintain the now-deprecated pure-Python “rocm-smi” package, and I’ve looked a few times at packaging rocm_smi_lib[1] to replace it, but the kinds of distro-friendliness issues you mention, e.g. [2][3], have so far been more than I was willing to work around.

I was also partially dissuaded by a general sense (which may or may not be accurate) that the main ROCm project’s issue tracker is dominated on both the filing and the responding side by high-volume end-user support questions, while the individual component projects have mostly technical bug reports but don’t always seem to have anyone reliably looking at them.

I’m happy to collaborate on work in this area as I am able, particularly—from a selfish perspective—if it leads to a maintainable rocm_smi_lib without too many downstream hacks, or if it eventually enables GPGPU in Darktable and/or BOINC without proprietary or unpackaged software. I think a lot of people would be *very* excited about that, if it is possible.

– Ben Beasley (FAS music)

[1] https://github.com/RadeonOpenCompute/rocm_smi_lib/
[2] https://github.com/RadeonOpenCompute/rocm_smi_lib/issues/84
[3] https://github.com/RadeonOpenCompute/rocm_smi_lib/issues/83

On 12/16/21 12:07, Jeremy Newton wrote:
Full disclosure, I am both a Fedora packager and an employee at AMD.
To be clear, the following is not at all endorsed by my employer; my interest and use of Fedora is purely a personal hobby and I would like to keep it that way.

There has been a recent effort to step up Debian packaging of ROCm, and would like to see if anyone has some interest in expanding the Fedora ROCm packages.

I see there's a few packages already, and I'm hoping to help with some internal processes to make ROCm more distro friendly, such as better FHS compliance, clearer licensing, etc.
Anyone interested? I would be happy to try to help or review package requests :)
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux