"Layered" build system

[Avi Kivity]

Hello,

I'd like to use koji as a layered build system.  I'm not sure that this is the right place, or that koji is the right tool.  If not, please let  me know what is.

We are building rpms against Fedora and CentOS/RHEL 7.  While all our dependencies are in Fedora, that's not the case for RHEL.  We would like to store our dependencies (updated rarely) as well as our product packages (updated often) in our local koji, but we'd like the rest of the distribution to be picked up from upstream, rather than having to import (and keep updating) all of our upstream dependencies into our local koji instance.

To make the case concrete, our non-upstream dependencies include gcc 5.3 (included in Fedora 23, but not in RHEL), binutils and isl (dependencies of gcc), boost (we need a later version than is available), ninja-build, ragel, gdb, and pyparsing.

Currently, we just regenerate them each build.  Ideally we pull them from our local koji instance.

Avi

[Alexander Todorov]

На 30.05.2016 в 14:40, Avi Kivity написа:
> Hello,
>
> I'd like to use koji as a layered build system.  I'm not sure that this is the right place, or that koji is the right tool.  If not, please let  me know what is.
>
> We are building rpms against Fedora and CentOS/RHEL 7.  While all our dependencies are in Fedora, that's not the case for RHEL.  We would like to store our dependencies (updated rarely) as well as our product packages (updated often) in our local koji, but we'd like the rest of the distribution to be picked up from upstream, rather than having to import (and keep updating) all of our upstream dependencies into our local koji instance.
>
> To make the case concrete, our non-upstream dependencies include gcc 5.3 (included in Fedora 23, but not in RHEL), binutils and isl (dependencies of gcc), boost (we need a later version than is available), ninja-build, ragel, gdb, and pyparsing.
>
> Currently, we just regenerate them each build.  Ideally we pull them from our local koji instance.

Hi Avi,
I think you're talking about this proposed feature:

https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service

I've not been tracking the progress but I think this is still ongoing.

--
Alex

[Avi Kivity]

> На 30.05.2016 в 14:40, Avi Kivity написа:
>
> Hi Avi,
> I think you're talking about this proposed feature:
>
> https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service

No, I'm not.  I'm not building docker images, but RPMs.  I'd like some of the dependencies to come from my koji instance, and some from upstream, this is the layering I was referring to.
> I've not been tracking the progress but I think this is still ongoing.

[Dan Horák]

On Mon, 30 May 2016 12:08:30 -0000
"Avi Kivity"  wrote:
> > На 30.05.2016 в 14:40, Avi Kivity написа:
> >
> > Hi Avi,
> > I think you're talking about this proposed feature:
> >
> > https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>
> No, I'm not.  I'm not building docker images, but RPMs.  I'd like
> some of the dependencies to come from my koji instance, and some from
> upstream, this is the layering I was referring to.

then you can use the "external repo" feature of koji - eg.
https://fedoraproject.org/wiki/Koji/ExternalRepoServerBootstrap
Then your koji can keep/build just your own rpms, but satisfy
depenedencies from eg. Fedora repos.

Dan

[Avi Kivity]

Thanks a lot. This is exactly what I was looking for.

[Philip Rhoades]

Avi,

On 2016-06-04 04:49, Avi Kivity wrote:
> Thanks a lot. This is exactly what I was looking for.

What was? - you appear to have deleted the response . . ?

P.
> --
> buildsys mailing list
> [e-mail]
> https://lists.fedoraproject.org/admin/lists/[e-mail]