[Pulp-dev] Composed Repositories

[Jeff Ortel]

On 05/15/2018 10:41 AM, Jeff Ortel wrote:
>
>
> On 05/15/2018 10:27 AM, Bryan Kearney wrote:
>> On 05/14/2018 03:44 PM, Jeff Ortel wrote:
>>> Let's brainstorm on something.
>>>
>>> Pulp needs to deal with remote repositories that are composed of
>>> multiple content types which may span the domain of a single plugin.
>>> Here are a few examples.  Some Red Hat RPM repositories are composed 
>>> of:
>>> RPMs, DRPMs, , ISOs and Kickstart Trees.  Some OSTree repositories are
>>> composed of OSTrees & Kickstart Trees. This raises a question:
>>>
>>> How can pulp3 best support syncing with remote repositories that are
>>> composed of multiple (unrelated) content types in a way that doesn't
>>> result in plugins duplicating support for content types?
>>>
>>
>> Both these examples are cases of RPM repos, yes? If so, does this
>> require a general purpose solution?
>
> The example in the thread is mainly RPM but there are other 
> repositories with shared content types.  Eg: OSTree repositories also 
> containing Kickstart Trees.

I also think there is value in not having the RPM plugin be a /mega/ 
plugin that knows how to deal with several complicated types of content 
(like in pulp2).  Making each plugin responsible for specific closely 
related types of content would make them more maintainable.

>
>>
>> -- bk
>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180515/e7c27590/attachment.htm>