[CentOS-devel] RFC: CentOS 8 Repository Structure

On 24/06/2019 13:09, Karanbir Singh wrote:
> 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.
> 

Again, this is *how* you see this, but it can differ from how that will
be composed, reason why we probably need a kind of formal plan (in the
wiki ?) to have $latest version of this thread, instead of trying to
read "between the lines" what was said or not, etc .. :-)


-- 
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20190625/ad4a533a/attachment-0004.sig>