I thought it'd be a good time to mention this again afer the thread
about hammer_cli_foreman_tasks, which was added to the Katello repos.
I think Katello people seem to prefer the way we're doing things, but
I'm not sure I understand. That's probably a product of having done far
more foreman packaging than for Katello, but…
hammer_cli_foreman_tasks has it's own rel-eng setup, and stores the
.spec file locally in its repo. Howiever, the comps are stored in the
Katello repo - which other than the fact Katello uses it, makes no sense
to me. A change, or adding a new package could require commits to
Is there a reason we can't adopt foreman-packaging or our own
katello-packaging? Nobody is left wondering what to update, or where a
spec file is, and also - if a particular package update breaks Katello.
I think that last one is important.
If we were to centralize packaging all in one place for both foreman and
katello, we could ensure the Katello test suite is run whenever our
dependencies are updated, and we'd catch the problem of Foreman making
changes to packages that Katello uses much quicker.
I realize that's increasing the load on our already taxed Rackspace
budget, but the amount of time wasted when deps break Katello is really
far too much.
Anyway, just a thought…
···-- Best Regards,
Red Hat Engineering