runtime vs build dependencies in making metapackages?

[Ryan Schmidt]

On Apr 5, 2009, at 14:24, Allen McBride wrote:

> In trying to make an mdmg for GNU Solfege, I first installed a  
> clean copy of MacPorts, then used "port -f destroot solfege", which  
> I now know was wrong.  But I counted 86 dependencies installed.   
> Then I did "port mdmg solfege", and counted 51 dependencies that MP  
> tried (and failed, of course) to make packages of.
>
> Now I know, or think I know, that the correct way to do this is to  
> do "port -f destroot" for each dependency, and then "port mdmg  
> solfege".  But on which list do I use "port -f destroot", the 86  
> member list or the 51?  Is it that, in making a metapackage, I only  
> need to worry about runtime dependencies, because build  
> dependencies will already be included in the solfege binary?  And  
> apparently I've got 51 runtime dependencies, and the rest are build  
> deps?  That would all make sense to me, but I'm just speculating.

I haven't used "port mdmg" myself so I can't advise you specifically  
for that.

I can explain that a port's build dependencies are only needed to  
build the software, not to run it. Therefore, there's no reason to  
include build dependencies into the binary mdmg package.