From: FiCacador <FiCacador@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: ROCm core and OpenCL
Date: Fri, 15 May 2020 00:51:51 +0200 [thread overview]
Message-ID: <20200514225151.ugvEw5w99GbosjPUFqfXzw7C97UXhjMGPBuJNv3kmTs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21153@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
New comment by FiCacador on void-packages repository
https://github.com/void-linux/void-packages/pull/21153#issuecomment-628926306
Comment:
It's not repurposing, it's installing only part of the components. The same can be done on Debian based distros, just install the necessary .debs for OpenCL to work. Or better yet, [the installer has options to install only the OpenCL components](https://math.dartmouth.edu/~sarunas/amdgpu.html).
Is it wrong to add a package that corresponds to one possible installation?
What if those necessary components are added individually, with dependencies (like AUR's [opencl-amdgpu-pro-pal](https://aur.archlinux.org/packages/opencl-amdgpu-pro-pal))?
Both approaches are in the AUR, and both work.
I just checked the [Gentoo wiki](https://wiki.gentoo.org/wiki/OpenCL#AMD), it mentions [dev-libs/amdgpu-pro-opencl](https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/amdgpu-pro-opencl/amdgpu-pro-opencl-19.30.838629.ebuild), doesn't look too different to me from AUR's [opencl-amd](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=opencl-amd).
All I'm trying to defend is that there is no reason for ROCm-OpenCL-Runtime and opencl-amdgpu-pro to supersede one another. One can keep a system open source, the other has better hardware support and performance. On an APU with iGPU or a navi GPU ROCm isn't even an option.
next prev parent reply other threads:[~2020-05-14 22:52 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 13:34 [PR PATCH] " ahesford
2020-04-19 15:24 ` [PR PATCH] [Updated] " ahesford
2020-04-19 15:57 ` ahesford
2020-04-19 19:02 ` ahesford
2020-04-20 2:02 ` ahesford
2020-04-28 14:00 ` ahesford
2020-04-28 15:14 ` ahesford
2020-04-28 17:34 ` ahesford
2020-04-28 17:34 ` ahesford
2020-04-28 17:38 ` ahesford
2020-04-28 18:09 ` ahesford
2020-04-28 18:44 ` [PR PATCH] [Updated] " ahesford
2020-04-28 19:59 ` ahesford
2020-04-30 19:05 ` ahesford
2020-04-30 19:12 ` ahesford
2020-04-30 19:22 ` ahesford
2020-04-30 19:32 ` ahesford
2020-04-30 19:35 ` ahesford
2020-04-30 19:38 ` ahesford
2020-05-01 4:57 ` lemmi
2020-05-01 5:10 ` ahesford
2020-05-01 5:12 ` ahesford
2020-05-01 14:04 ` [PR PATCH] [Updated] " ahesford
2020-05-01 19:36 ` ahesford
2020-05-02 1:34 ` ahesford
2020-05-02 3:29 ` ahesford
2020-05-05 14:24 ` ahesford
2020-05-05 14:26 ` ahesford
2020-05-07 14:18 ` ahesford
2020-05-07 16:01 ` ahesford
2020-05-08 14:40 ` ahesford
2020-05-11 18:02 ` ericonr
2020-05-11 18:07 ` ahesford
2020-05-11 18:07 ` ahesford
2020-05-11 18:52 ` [PR PATCH] [Updated] " ahesford
2020-05-11 20:03 ` ahesford
2020-05-14 18:04 ` FiCacador
2020-05-14 18:04 ` FiCacador
2020-05-14 19:13 ` ahesford
2020-05-14 19:14 ` ahesford
2020-05-14 22:51 ` FiCacador [this message]
2020-05-15 0:07 ` ahesford
2020-05-15 1:30 ` fosslinux
2020-05-15 3:31 ` FiCacador
2020-05-15 3:32 ` FiCacador
2020-05-15 6:54 ` fosslinux
2020-08-04 17:13 ` [PR PATCH] [Updated] " ahesford
2020-08-04 17:13 ` ahesford
2020-08-04 17:16 ` [PR PATCH] [Closed]: " ahesford
2020-08-04 17:16 ` [PR PATCH] [Updated] " ahesford
2020-08-04 17:19 ` ahesford
2020-08-04 17:24 ` [PR PATCH] [Updated] " ahesford
2020-08-18 18:36 ` aurieh
2020-08-18 18:38 ` aurieh
2020-08-18 18:39 ` aurieh
2020-08-18 19:46 ` ahesford
2020-08-20 18:50 ` [PR PATCH] [Updated] " ahesford
2020-12-21 7:32 ` fosslinux
2020-12-21 11:58 ` ahesford
2021-02-15 5:19 ` ahesford
2021-02-15 5:19 ` [PR PATCH] [Closed]: " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200514225151.ugvEw5w99GbosjPUFqfXzw7C97UXhjMGPBuJNv3kmTs@z \
--to=ficacador@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).