On 24/06/2019 13:05, Fabian Arrotin wrote: > On 24/06/2019 12:42, Karanbir Singh wrote: >> 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. >> > > Would be indeed worth clarifying, as I was under the impression that > Brian said the reverse with "all updates would land in BaseOS" and so > BaseOS would be a moving target ... > > @Brian : can we clarify once for all this ? > 2 diff things, a) BaseOS will get all the content from a point release and all updates will land in the same directory b) we snapshot the repo metadata and publish it in addition to the baseos repo ( what was called the kickstart repo ). we can do both. -------------- 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/53f6a26b/attachment-0008.sig>