On 19/06/2019 19:42, Brian Stinson wrote: >> >> I need to be able to run installs against a mirror, weeks and months >> >> apart and arrive at the same payload installed exactly. >> again, this maybe just a case of publishing a 2nd set of metadata rather >> than retain the base rpm set, but we need to retain this functionality. > Wouldn't pinning versions be better here if that's what you need? If you > took that same kickstart over to a RHEL machine, you'd get the updates > over there. no, you would get a point release ( same as media .. ) if you wanted to. I want to make sure we dont lose that ability in CentOS, so were going to need to do this. > > Seems to me like delivering the updates separately goes against our > community recommendations anyways (i.e. the first thing we say in irc is > "did you run yum/dnf update?"). we dont however, ask people to install arbitary untested trees. Help me qualify the concern in an extra set of metadata to match point release media ? regards, -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20190624/63999cdd/attachment-0008.sig>