Re: when using autoyast, can a specific version of a package be required?

El lunes, 29 de junio de 2020 16:35:30 (WEST) Brian Reichert escribi=F3:
> On Mon, Jun 29, 2020 at 10:53:05AM -0300, Perry Werneck wrote:
> > Hi,
> >=20
> > I think you can do this using a meta-package requiring the bash in the
> > exat
> > version you need.
>=20
> I suppose I should be transparent about what I'm trying to accomplish:
>=20
> At $WORK, we produce SUSE-based appliances for customers, ultimately
> delivered as an OVA.
>=20
> Internally, we do not use repositories for deployment via autoyast;
> we have some home-rolled mechanism that is showing it's age.
>=20
> 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.)

Perhaps I am missing something, but mixing packages for multiple releases i=
n=20
the same repository does not look like a good idea at all. Why not just hav=
ing=20
a separate repository for each release? OBS[1] can help with that.
[..]

Regards,
Imo

[1] https://openbuildservice.org/

=2D-=20
Imobach Gonz=E1lez Sosa
YaST Team at SUSE LLC
https://imobachgs.github.io/



-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]