[Pulp-list] dropping el6 builds of Pulp

[Jeremy Audet]

> In theory, you can pip install pulp now right from the git repositories
if you just check out the desired release tags.

Is this true? Some of the Pulp-related git repositories (perhaps all of
them?) lack a setup.py file, which is the first thing I look for when
trying to install Python software. Additionally, it's unclear which git
tags should be checked out. For example, pulp_python has a tag named
'1.0-release'. Which Pulp releases does that tag work with? And pulp_rpm
has a tag named '2.9-release' - does this tag correspond to 2.9, 2.9.1,
2.9.2, etc?

> The challenge of course is that today the RPMs provide much more than
just the code; apache configs, /etc/pulp, /var/lib/pulp, selinux stuff,
startup scripts, etc. It would be great to move a lot of that work to a
config management system and treat that as an installer, which is probably
the biggest chunk of work currently necessary to make "pip install" a
viable deployment technique. This would be wonderful to have. Another great
benefit to this general effort is that it would open up the possibility of
installing Pulp on Debian-based systems.

Can we completely separate the installation and configuration steps? Could
we let the user install Pulp via whatever method they prefer, such as via
pip, dnf/yum, apt*, pacman, emerge, ansible, etc, and then let the user
also configure Pulp via either Ansible or manually?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20161129/97a11ac7/attachment.htm>