On Tue, May 03, 2011 at 07:41:47AM -0400, Vadym Chepkov wrote: > On Mon, May 2, 2011 at 4:20 AM, Dejan Muhamedagic <[email protected]> wrote: > > Hi Vadim, > > > > On Sun, May 01, 2011 at 10:53:44AM -0400, Vadym Chepkov wrote: > >> Hi, > >> > >> recent addition of vcenter external plugin generates dependency on exotic > >> perl(VMware::VIRuntime) package, majority won't use. > > > > The dependency is automatically generated by find-requires on RH > > distributions. Whether the package is exotic or not, depends on > > what you run. One could brand exotic just about any stonith > > plugin. > > But this is what I was changing, cluster-glue-fedora.spec is intended > to be used on RH distros, no? > Maybe "exotic" is a wrong choice of a word, but it is not part of > fedora or epel repositories > > > > > >> I propose to create a separate subpackage, cluster-glue-extras, for all > >> optional components > > > > That is a wrong place to fix this issue. We should not create an > > extra package just because find-requires (actually perl.req) > > cannot be told not to create a dependency on a module. > > Not sure what you mean a wrong place? You mean let packagers deal with it?
No, what I meant was to filter the dependency out. However, it is eventually up to the packagers to split packages in any way they feel like. I think that packaging is not exactly equal between various distributions. > Dependency can certainly be filtered out, but this would just mask the > problem, not solve it. I don't think that this is a problem at all. Whoever wants to use vcenter will have to install whatever the plugin needs. That's how it has always been with stonith plugins. Or do you propose to create a package per stonith plugin? > The module definitely needs this dependency, it is not a false finding > and I don't see how having an extra package can hurt anything. This is > a standard way to reduce amount of dependencies. For example, zabbix > can work with either mysql, postgres or sqlite as a backend. Instead > of forcing to install libraries to support everything, they have > subpackages that would pull with them only necessary components, when > desired backend is selected for installation. Right, but there's a limit to the number of backends. If we start creating packages because of dependencies for specific stonith modules there's no telling how many will we have in the end. Besides, the plugin can deliver at least its description for the interested user even without dependencies. Thanks, Dejan > Just a though, > > Vadym > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
