Re: Help with package that has a build dependency on a Linux binary

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Fri, May 17, 2019 at 09:52:43AM -0700, Jason Thorpe wrote:
> Sigh, ok :-)  Deep down, in the pit of my soul, I know it's the right thing to do.  I was, however, hoping that laziness would prevail :-)

:-)

> So, if I were to make this "amlogic-meson-fwtools" package, I have a couple of questions:
> 
> -- What's the correct way to express the run-time dependency on the Linux emulation package?

Just define the platform of the binary, and the dependencies.
E.g. for a program that just depends on suse*openssl, you'd do:

EMUL_PLATFORMS=         linux-x86_64
EMUL_MODULES.linux=     openssl

That's it!

> -- What's the correct way to express that there is NO BUILD-TIME dependency on this package?  These things aren't distributed as RPMs or anything, just naked binaries, but I'd want building a binary package to work.

Yeah, we don't have that. Runtime dependency (DEPENDS) currently
always implies build time dependency.

> Well, yes, it's working for me... but I want to make sure that I don't e.g. break bulk builds on PowerPC, or bulk builds on SmartOS / Illumos, etc.  So, I guess I'll make "u-boot for amlogic systems" an option that defaults to "on" for NetBSD on x86_64 and "off" for everything else, for the u-boot meta-package.

Sounds good.

Thanks,
 Thomas