[ovs-dev] [PATCH 2/2] debian: Created a debian equivalent to xen-bugtool

Ben Pfaff blp at nicira.com
Thu Sep 16 19:28:42 UTC 2010

On Thu, Sep 16, 2010 at 12:23:35PM -0700, Ethan Jackson wrote:
> > When we add this to the Debian packaging we should also make sure to add
> > proper dependencies; for example, the script uses bzip2 so that should
> > be a dependency.  If there are lots of these dependencies then we'll
> > have to drop some of them (i.e. hdparm or lvdisplay would probably be no
> > great loss) or break this program into a separate openvswitch-bugtool
> > package.
> Couple of things.
> 1) I'm not sure why they are bothering with bzip2.  I might just
> change that to gzip so we can remove the dependency

Fine with me.

> 2) I think there is a distinction between dependencies which are
> required for the script to run (like python) and soft dependencies
> which result in more debugging information, but aren't strictly
> necessary for the script to run (like hdparm).  I'm not sure there is
> a lot of value in adding those things to the package, if the system
> already has them installed then great, we will use them.  Otherwise we
> just won't get that debugging output.

Such dependencies should then be Recommends: or Suggests: according to
the Debian policy manual.  Up to you to decide I think:


        This declares an absolute dependency. A package will not be
        configured unless all of the packages listed in its Depends
        field have been correctly configured.

        The Depends field should be used if the depended-on package is
        required for the depending package to provide a significant
        amount of functionality.

        The Depends field should also be used if the postinst, prerm or
        postrm scripts require the package to be present in order to
        run. Note, however, that the postrm cannot rely on any
        non-essential packages to be present during the purge phase.


        This declares a strong, but not absolute, dependency.

        The Recommends field should list packages that would be found
        together with this one in all but unusual installations.


        This is used to declare that one package may be more useful with
        one or more others. Using this field tells the packaging system
        and the user that the listed packages are related to this one
        and can perhaps enhance its usefulness, but that installing this
        one without them is perfectly reasonable.

More information about the dev mailing list