On Mon, Jun 29, 2020 at 10:53:05AM -0300, Perry Werneck wrote:

Hi,

I think you can do this using a meta-package requiring the bash in the exat version you need.

I suppose I should be transparent about what I'm trying to accomplish: At $WORK, we produce SUSE-based appliances for customers, ultimately delivered as an OVA. Internally, we do not use repositories for deployment via autoyast; we have some home-rolled mechanism that is showing it's age. I've been exploring, with some success, using a single private repository, to contain our RPMs of multiple releases, and with 'zypper', I can with fine detail, describe installation and upgrade tasks. (I'm using 'createrepo' to manage that metadata.) I'm now exploring deployments via autoyast, and am finding I don't have the fine-grained control that zypper offers, to declare 'deploy with version 4 vs version 5'. I was considering your suggestion, maintaining a meta-RPM that called out specific dependencies, but as I would implicitly want multiple versions of that meta-RPM, I still suffer from the constraint of <package> in autoyast not letting me call out version numbers. It's entirely possible there's richer metadata in my repo I can manage (for example, I don't really get 'products' yet) that would get me over this planning, if this tactic was in fact possible.

-- Perry Werneck Bras??lia/DF

-- Brian Reichert <reichert@numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org