On Sep 2, 2017 6:17 AM, "Ewoud Kohl van Wijngaarden" < ew...@kohlvanwijngaarden.nl> wrote:
On Fri, Sep 01, 2017 at 07:48:19PM -0400, Eric D Helms wrote: > As a lead-in to being working towards migrating Katello's packages to the > foreman-packaging repository, I'd like to propose a slight re-organization > of the repository. As well, to seek any other ideas or problems any might > see with the proposal. > > Currently, the packaging repository is a flat structure with all packages > being represented by a directory containing sources and a spec file. When > looking at it, I find it hard to think about them in an organized manner > given we separate by repository into foreman and foreman-plugins (and > eventually katello repositories). Thus, my proposal is to let the packaging > repository reflect the repository organization by moving things into the > following directories: > > foreman-packaging > - foreman > - plugins > - katello > - katello-client > > > Thoughts? > It makes sense to me and I have the same problem but it does make me wonder how we deal repo boundries/repoclosure. Plugins probably needs foreman where katello probably requires foreman and maybe plugins. If a package from plugins is now required in foreman, is it moved? Yes. The breakdown in the packaging repository would essentially be by repository. So if something lives in the foreman repository it lives in the foreman folder. Repository requires and repoclosure should not be affected by this change. I assume katello-client is supposed not to require any other repos, just base OS and possibly EPEL. If a package is needed in both foreman and katello-client, should it be copied? That's a good question. I would say it should go in the most base of repositories in a heirarchy given that koji only lets you have a single build in it but can be tagged across. I think this situation should be rare. Long term/big picture: I know we have pulp and candlepin. Where do they fit in? Should katello eventually be merged into plugins? We don't manage Pulp and Candlepin packaging from that perspective. We make use of their builds but the process is separate. I think most would probably argue for putting Katello into the plugins repository once we figure out a few constraints within our CI. Eric -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
