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

Re: Joining ROCm team, ectrans



On 2024-10-12 21:06, Cordell Bloor wrote:
> On 2024-10-12 11:25, Christian Kastner wrote:
>> So do we want to use "rocm" and accept some possible confusion and/or
>> apt_preferences(5) trickery requirement, or should we go with "rocm-deb"
>> or "rocm-dist" or similar. Likewise for -dev.
> 
> This has been a problem for rocminfo and rocm-smi since Ubuntu 22.04. It
> is also a problem for Red Hat users now that ROCm packages are available
> in the EPEL.

OK, so the only proper fix seems to be upstream indeed.

> AMD's official installation instructions for ROCm set
> package priorities to force the installation of rocminfo and rocm-smi
> from the rocm repo, but I'm not a fan of this solution.
>
> rocminfo installed to /usr/bin and rocminfo installed to /opt/rocm
> are not really interchangeable. When one installs into the system
> PATH and one does not, they are fundamentally different packages and
> should have different names, not just different versions.

In this case, rocminfo goes a step into the right direction: it installs
to /opt/rocm and uses update-alternatives(1) to point /usr/bin/rocminfo
to it.

If Debian's rocminfo were co-installable, update-alternatives could be
used to switch /usr/bin/rocminfo to whatever version is desired.

I did not look, but I assume that we have a few other executables beyond
rocminfo, rocm-smi with this problem: amd-smi, hipcc, ...
> AMD's amdgpu repository adds the suffix "-amdgpu" to all packages that
> it provides. It is my opinion that AMD's 'rocm' repo should do something
> similar. It would likely add the prefix "amd-" to all packages [2].
>
> I think that Jeremy, Tom and I need to hammer on this issue with AMD's
> packaging teams. To prevent conflicts, it should really AMD's
> responsibility to choose a consistent naming convention for their
> repository.

That would be great.

> [2]: I wonder if this might be an issue for some tools as packages are
> split into different directories based on the first letter of the
> package name? Or maybe there aren't enough packages for it to matter...

I don't quite follow, do you mean in the Archive?

Best,
Christian


Reply to: