On Sat, May 20, 2006 at 04:42:09PM +0200, Jose Carlos Garcia Sogo wrote: > > Still, the Build-Depends contains things like cli-common-dev (>= 0.4.0) > > [i386 powerpc amd64 ia64]. Doesn't that result in build failure on other > > architectures? > > Shouldn't happen, as you are declaring that build-dependency only on > those arches, while it won't be tried to be satisfied in other places.
But dh_clideps is part of cli-common-dev, so if this package is built
on, for example, m68k, it will fail when debian/rules tries to run that.
That's why I had this kludge:
> > > - which dh_makeclilibs && dh_makeclilibs -m $(UPVERSION) -l
> > > $(NEXT_UPVERSION) || true
> > Unfortunately there are no manual pages for dh_makeclilibs,
> > dh_installcligac and dh_clideps. Can you tell me what the -d options
> > does? And is the -p option necessary?
>
> -d tries to remove duplicate dependencies.
Why isn't this the default behaviour of those debhelper scripts?
> -p is there to make those
> commands to run only on that package, instead of the whole set. It does
> not have any sense to run it on more packages than that one.
Ok, not _required_ then :)
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
