<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 05/15/2018 11:59 AM, Brian Bouterse
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAcvrTEdcN2tGUCoUmvQ8F1VqNjxeNEVOcgtbqvhwDx+KCdiwQ@mail.gmail.com">
<div dir="ltr">
<div>I agree these are specific cases for a few content types
that are used by multiple plugins. I think the most productive
thing would be for us to talk in specific only about kickstart
trees being shared between RPM and ostree. It would be much
easier to generalize after building something specific once (I
think).</div>
</div>
</blockquote>
<br>
This discussion wasn't about generalization or abstraction. It's
about dealing with remote repositories that are different
combinations of common content types. That said, while searching
for concrete examples (use cases), it turns out these combinations
don't really exist. In pulp2, the RPM plugin is used to sync ISO
repositories but they are not combined with other content types in
the same repository. Kickstart trees are only combined with YUM
repositories. Combination OSTree/KS-tree repositories aren't really
a thing.<br>
<br>
I think this thread can end here.<br>
<br>
<blockquote type="cite"
cite="mid:CAAcvrTEdcN2tGUCoUmvQ8F1VqNjxeNEVOcgtbqvhwDx+KCdiwQ@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>A mentor I had once told all software that lives long
enough goes through 3 phases. (1) A concrete implementation
(2) generalizing that implementation, and then (3) rewriting
that implementation because of everything you didn't know
before. I'm advocating for us to think about the problem as a
specific plugin problem (step 1) and then after that is done,
to look at generalizing it (step 2).<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 15, 2018 at 11:27 AM, Bryan
Kearney <span dir="ltr"><<a
href="mailto:bkearney@redhat.com" target="_blank"
moz-do-not-send="true">bkearney@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On 05/14/2018 03:44 PM, Jeff Ortel wrote:<br>
> Let's brainstorm on something.<br>
> <br>
> Pulp needs to deal with remote repositories that are
composed of<br>
> multiple content types which may span the domain of a
single plugin. <br>
> Here are a few examples. Some Red Hat RPM
repositories are composed of:<br>
> RPMs, DRPMs, , ISOs and Kickstart Trees. Some OSTree
repositories are<br>
> composed of OSTrees & Kickstart Trees. This
raises a question: <br>
> <br>
> How can pulp3 best support syncing with remote
repositories that are<br>
> composed of multiple (unrelated) content types in a
way that doesn't<br>
> result in plugins duplicating support for content
types?<br>
> <br>
<br>
<br>
</span>Both these examples are cases of RPM repos, yes? If
so, does this<br>
require a general purpose solution?<br>
<span class="HOEnZb"><font color="#888888"><br>
-- bk<br>
<br>
<br>
</font></span><br>
______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" moz-do-not-send="true">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>