Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Makefile.groups: remove kazoo group and move kazoo to rabbitmq
- Loading branch information
1 parent
f503615
commit 71d42ee
Showing
1 changed file
with
2 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
71d42ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@linuxmaniac what's the reasoning for this ?
71d42ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lazedo now we have rabbitmq group, lets use it. Makes no sense to me having kazoo group since both depends on librabbitmq library and
rabbitmq
name seems more generic thankazoo
71d42ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@linuxmaniac that would create problems when upgrading. also, why would kazoo require rabbitmq module to be installed ? everything that rabbitmq module does, kazoo module already does it, why is this module needed ?
71d42ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see in the Makefile that kazoo depends on more libs, not only rabbitmq. Having it packaged alone is probably better.
71d42ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lazedo @miconda reverted. But having more and more debs for single modules is not a good idea in my opinion. We should reach to a balance between dependences and number of module packages
71d42ee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not a big fan of too many packages either (on the other hand I mainly install from git), but there are also cases when a module from a group has plenty of dependencies that one could think of why installing them if needing only another module from a group.
Is there a recommendation from Debian in similar cases? I was trying to analyze on this topic in the past and it seems that other apps/projects with modules have typically one package per module. I noticed that for PHP, with the typical modules I use there (php mysql, gd, curl, ...).
Maybe we should open an issue to debate the packaging. You can propose a grouping that you think it is the best and the others can contribute from there.