Is there a better way to achieve the results with less
risk?
What I do for this is run podman containers. I create local images of
centos+epel, then use a helper script to run them with a podman volume
mounted at /var/cache/{yum,dnf}. With my script I can run repoquery
commands prefixed by a distro identifier.
c7 repoquery --whatprovides webserver
This also has the benefit of being able to start a container
interactively, install packages, and then throw it away when you're
done, with zero risk of installing packages on the host. If this
approach is interesting to you I can put my scripts in a public repo
somewhere.
On Tue, Jul 21, 2020 at 3:34 PM Miro Hrončok <mhroncok(a)redhat.com> wrote:
On 21. 07. 20 22:14, Kevin Fenzi wrote:
> Well, not sure. Is there some way to put the repo files in a doc space
> or something and only get repoquery to use them, not normal dnf
> commands? I can't think of how to make it work, but perhaps dnf people
> could? could we request a special/etc/dnf/repoquery.d/ dir or
> something?
I could not find anything remotely like this in dnf documentation. I can
possibly open and RFE, but given how the dnf devs are swamped I don't think it
would be realistic to expect this to land any time soon.
> Failing that, can they at least have a big comment block explaining that
> you shouldn't use them to install any packages with?
Can do. I can even put that into the package descriptions.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
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/epel-devel@lists.fedoraproj...
--
Carl George