From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: "St Savage, Shane" <Shane@axiomdatascience.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: infiniband-diags can't be installed in Fedora CoreOS due to perl dependency
Date: Mon, 14 Aug 2023 12:32:24 -0300 [thread overview]
Message-ID: <ZNpJCGSi7Ei1IN0A@ziepe.ca> (raw)
In-Reply-To: <20230813103305.GJ7707@unreal>
On Sun, Aug 13, 2023 at 01:33:05PM +0300, Leon Romanovsky wrote:
> On Sat, Aug 12, 2023 at 04:40:57PM +0000, St Savage, Shane wrote:
> > Hi all,
> >
> > Just wanted to report that infiniband-diags cannot currently be installed in Fedora CoreOS because the perl dependency is explicitly forbidden.
> >
> > https://github.com/coreos/fedora-coreos-config/blob/testing-devel/manifests/fedora-coreos.yaml#L170
> >
> > This is a bit unfortunate because it also prevents usage of all the non-perl utilities (ibstat, etc) included in infiniband-diags.
> >
> > Would it make sense to split the perl utilities to a separate package infiniband-diags-perl so that the C and shell utilities in infiniband-diags can be installed without the perl dependency?
>
> I suggest to remove perl dependency from rdma--core.spec and install
> perl-dependant scripts only if perl is found on the system.
That is not how packaging is supposed to work
Everything should be installed always
This is really a Fedora question, we just follow what they
decide. Most likely the right answer is to put this kind of stuff in a
container and not run on the minimal coreos image.
Jason
next prev parent reply other threads:[~2023-08-14 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 16:40 infiniband-diags can't be installed in Fedora CoreOS due to perl dependency St Savage, Shane
2023-08-13 10:33 ` Leon Romanovsky
2023-08-14 15:32 ` Jason Gunthorpe [this message]
2023-08-14 18:20 ` Leon Romanovsky
2023-08-15 18:36 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2023-08-13 0:20 Shane St. Savage
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=ZNpJCGSi7Ei1IN0A@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Shane@axiomdatascience.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.