Great, thanks for that. This makes building devel/subversion quite painful as it means there is a dependency on gnome-keyring which brings in loads of cruft. I suppose the answer to issues like this is submit a patch to add a pseudo flavour to disable specific multi-packages.
Thanks for your help, it has saved much hair pulling. Rob > On 19 Jun 2016, at 21:22, Stuart Henderson <s...@spacehopper.org> wrote: > > On 2016/06/19 18:57, Rob wrote: >> Hi, >> >> I’ve been pulling my hair out for the past week trying to find out why I >> can’t build multi-packages using dpb(1) on 5.9, or rather why dpb(1) is >> choosing to build all of a ports sub-packages. >> >> I have been trying to build databases/postgresql,-server, among other. >> Unfortunately, this builds all of the PostgreSQL sub packages (e.g. >> -plpython, -docs). The command line I’m using is: >> >> # /usr/ports/infrastructure/bin/dpb databases/postgresql,-server >> >> I’ve tried searching, but I’ve been unable to find any other people >> reporting this problem. Digging through the source I can see that >> SUBDIR=databases/postgresql gets set within DPB::Vars::run_command() when >> ‘make dump-vars’ is run and this shows all of the sub/multi-packages, these >> then get enabled and added to the build queue. I think if >> SUBDIR=databases/postgresql,-server was set this would eliminate the problem. >> >> Am I correct in assuming dpb(1) supports this type of pkgpath (e.g. >> databases/postgresql,-server)? If so, does this functionality work as >> expected under a vanilla 5.9, from the release ISO or built from the >> OPENBSD_5_9 CVS tag? >> >> thanks >> >> Rob > > Unless there is a "no_xx" PSEUDO_FLAVOR (not the case for postgresql), > you can't control which parts of a multi-package port are built, whether > using dpb or not. > >
