Closed jeffwidman closed 7 years ago
Maybe @spladug can comment on this. I think he requested those Debian files to be added initially.
I think it's fine to remove the files from this repository as they're maintained in Debian itself these days. Removing them won't mean having to remove it from Debian.
That said, Kazoo is a dependency of several other packages in Debian and is actively maintained there. I don't think it'd be helpful to try to get the library removed.
Ok, sounds to me like the Debian files are unused and removing them from this repo shouldn't be a problem.
Since the python-kazoo package in Debian is maintained elsewhere, we don't have to change anything about it or make decisions here.
Can we remove the Debian packaging files from this project?
In the worlds where I work/play, no one installs python libraries using debian packages.
Instead they would do
apt-get install python-pip
followed bypip install kazoo
.The one exception being system-focused libraries like
gevent
where there is a significant risk of stability issues with various flavors of Linux--there they might install the OS-pre-packaged version to be sure it was tested with their OS.Given all this, I wonder why we need to keep the Debian packaging around?
pip
were not quite so stable/ubiquitous workflow.kazoo
itself.kazoo
itself might necessitate removing thepython-kazoo
package from the Debian project as well. This shouldn't cause any problems because of the aforementioned workflow of installingpip
followed bypip install kazoo
. I actually see removing this debian package from the debian projects as a good thing, because it frees up the maintainers to spend time on projects that do actually are better shipped as debian packages.If the other maintainers are on board with this change, I am happy to handle putting together a PR and/or following up with other projects affected by this change.