Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove debian packaging files? #465

Closed
jeffwidman opened this issue Jul 24, 2017 · 3 comments · Fixed by #468
Closed

Remove debian packaging files? #465

jeffwidman opened this issue Jul 24, 2017 · 3 comments · Fixed by #468
Assignees

Comments

@jeffwidman
Copy link
Member

jeffwidman commented Jul 24, 2017

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 by pip 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?

  • I suspect the Debian packaging was added during a time when PyPI and pip were not quite so stable/ubiquitous workflow.
  • Most of these files have not been updated in 5 years. Perhaps they don't need updating, but I suspect they do have some bitrot.
  • I'm not sure how this might affect https://github.com/openstack/deb-kazoo, which appears to be an exact mirror of this project, despite the description for that repo saying that it's just the debian packaging for this project. I've never used OpenStack, perhaps they could simply bundle the Debian build scripts, without including kazoo itself.
  • Removing the debian packaging files from kazoo itself might necessitate removing the python-kazoo package from the Debian project as well. This shouldn't cause any problems because of the aforementioned workflow of installing pip followed by pip 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.

@hannosch
Copy link
Contributor

Maybe @spladug can comment on this. I think he requested those Debian files to be added initially.

@spladug
Copy link
Contributor

spladug commented Jul 24, 2017

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.

@hannosch
Copy link
Contributor

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.

jeffwidman added a commit that referenced this issue Jul 24, 2017
Removing the debian packaging files as they're maintained in Debian
itself these days. Removing them won't mean having to remove it from
Debian.

See further discussion in #465

closes #465
hannosch pushed a commit that referenced this issue Jul 24, 2017
Removing the debian packaging files as they're maintained in Debian
itself these days. Removing them won't mean having to remove it from
Debian.

See further discussion in #465

closes #465
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants