On 12/15 18:55, Chuck Yerkes wrote:
> I didn't find this in the archives, but I didn't read everything.
> 
> I'm fairly well used to OpenBSD and one thing they do that's
> nice is that BEFORE the install target is a "package" target.
> Always.
> 
> Which means if I make (say) spam-assassin, I have packages of
> ALL the dependancies.
> 
> It means they install into $PACKAGE/work/fake-install/, not
> the live tree.
> 
> I can live with installing then getting a package, but I'm
> having to manually track dependancies to FIND them to make
> packages.

As Eric already said, the package package target will do that for you.

If you wanted to install dependencies from binary packages, you would
set DEPENDS_TARGET to bin-install.
 
> Oh, it would also be nice to be able to differentiate between
> tools needed to run and tools needed to build.  I may need gmake
> to build something, but its moot once the build is done.
> Any tools that anwser this?
>     "show me the chain of dependancies for spamassassin"

lothar:.../pkgsrc/mail/spamassassin$ make print-run-depends-list
This package requires package(s) "p5-Digest-HMAC>=1.0
p5-Digest-MD5>=2.00 p5-Digest-MD5>=2.12 p5-Digest-SHA1-[0-9]*
p5-Digest-SHA1>=1.00 p5-Digest>=1.00 p5-HTML-Parser>=3.29
p5-HTML-Tagset>=3.0 p5-IO-Socket-SSL>=0.92 p5-MIME-Base64>=2.11
p5-Net-DNS>=0.29 p5-Net-SSLeay-[0-9]* perl>=5.0 perl>=5.6.0" to run.

You can just use run-depends-list to get it in an easier-to-parse
format, but you'll have to weed out the duplicates.