Re: include in mentors faq? Re: DFSG compliant packages (Solution)
On Sun, Oct 02, 2005 at 04:57:08PM -0700, Russ Allbery wrote:
> Justin Pryzby <justinpryzby@users.sourceforge.net> writes:
> > On Sun, Oct 02, 2005 at 12:08:07AM +0200, Ghe Rivero wrote:
>
> >> Another one, it depends on some tools, like rpm2cpio to updated
> >> properly. Should those tools be included as a dependecies on the control
> >> file? It's not build time or a runtime depencie, Any filed to an
> >> update-dependencie? :)
>
> > It has to be a dependency of the new version of the package; this is
> > policy 7.2:
>
> > 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.
>
> That's a different sort of maintainer script. That section is for the
> scripts that are run as part of package installation, which this isn't.
>
> Depends is for things the package needs to run. Build-Depends is for
> things the package needs to build. Things the package needs to run
> get-orig-source or the like are neither, and therefore don't need to be
> listed, IMO.
> >> Another one, it depends on some tools, like rpm2cpio to updated
> >> properly. Should those tools be included as a dependecies on the control
and
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.
Upgrading is typically in the postinst. Or did I misunderstand?
--
Clear skies,
Justin
Reply to: