On Mon, Nov 22, 2010 at 07:00:38PM -0400, Joey Hess wrote: > Roger Leigh wrote: > > However, if I did want a complete list of all packages, all arch or > > all indep packages irrespective of what is currently in > > DH_INTERNAL_OPTIONS, it would be nice to have a --force|-f option > > or the like to do this so I don't need to use debhelper internals. > > I'm not clear on what you'd expect to find in that list. Eg, should it > contain packages that are only built on other architectures?
That's a good question. For the uses I was thinking of, I wanted to
compare a package (or set of packages) with the list of packages
being built on the current architecture to see if there was an
intersection between the two sets.
This would be the same output you would get from running
dh_listpackages in the source tree without involving dh or
DH_INTERNAL_OPTIONS.
My initial use was to use it like in the example shown in my initial
mail, to find out if we are building arch or indep packages:
target:
ifneq (,$(strip $(foreach V,$(shell dh_listpackages),$(filter $(V),$(shell
DH_INTERNAL_OPTIONS= dh_listpackages -a)))))
@echo Arch
endif
ifneq (,$(strip $(foreach V,$(shell dh_listpackages),$(filter $(V),$(shell
DH_INTERNAL_OPTIONS= dh_listpackages -i)))))
@echo Indep
endif
But there's obviously a simpler solution, as I showed.
There are less complicated uses for the information during a package
build, such as:
- checking if a package is to be built (irrespective of how invoked
by dh)
- and more complex conditionals where the packages to check are in
both the arch and indep lists and you need the full list
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
