RepoFunnel and the Software Component Pipeline

[Nick Coghlan]

On 23 August 2015 at 23:44, Colin Walters <walters at verbum.org> wrote:
>
> On Fri, Aug 21, 2015, at 06:39 PM, Nick Coghlan wrote:
>> which are then hard to replicate across machines (e.g. a
>> separate laptop and workstation, or multiple remote servers).
>
> This is a space that would seem to be solved well by config
> management/automation tools; e.g. I use Ansible for most
> of my personal machines, and hook up any COPR or other
> repositories that way:
>
> https://github.com/cgwalters/ansible-personal/blob/master/roles/icarus-system/tasks/devel-packages.yml#L7

Configuration management is only an effective approach for centrally
controlled systems, and requires a high level of system administration
expertise on the part of the end user. I'm not the least bit
interested in becoming a system administrator, and I certainly don't
want to be maintaining my own configuration management scripts for my
personal devices - I want my systems to be as close as possible to the
default state in order to maximise the chances of trouble-free
upgrades.

Centralised configuration management also doesn't work for easily
defining and sharing project specific repos containing pre-integrated
package sets (e.g. the beaker-project.org repos, which provide not
only Beaker, but also any dependencies which aren't part of the
underlying operating system).

Filtered repo definitions, by contrast, are very easy to federate
across different users, and very easy to consume when building
container and machine images (regardless of the image creator's
preferred choice of configuration management tool).

Regards,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia