Re: deactivating build deps

2018-01-02 Thread Jan Stary
On Jan 02 14:37:00, ryandes...@macports.org wrote:
> On Jan 2, 2018, at 13:33, Jan Stary wrote:
> > 
> > Deactivatng e.g. man warns me that 
> > 
> >  Note: It is not recommended to uninstall/deactivate a port that has
> >  dependents as it breaks the dependents.
> >  The following ports will break: lirc @0.9.4d_3
> > 
> > It's a build dependency, not a run dependency or a lib dependency.
> > Does the deactivate/uninstall differentiate between those?
> 
> Yes, MacPorts differentiates. I don't know why you would see that message 
> when deactivating a build dep.  
> 
> Your pull request shows that you originally added man as a library dep not a 
> build dep. If you installed lirc in that state, that's what got recorded in 
> the registry and would account for the message. 

Yes, it was an artifact of that mistake. Thanks.

Jan



Re: deactivating build deps

2018-01-02 Thread Ryan Schmidt
On Jan 2, 2018, at 13:33, Jan Stary wrote:
> 
> Deactivatng e.g. man warns me that 
> 
>  Note: It is not recommended to uninstall/deactivate a port that has
>  dependents as it breaks the dependents.
>  The following ports will break: lirc @0.9.4d_3
> 
> It's a build dependency, not a run dependency or a lib dependency.
> Does the deactivate/uninstall differentiate between those?

Yes, MacPorts differentiates. I don't know why you would see that message when 
deactivating a build dep.  

Your pull request shows that you originally added man as a library dep not a 
build dep. If you installed lirc in that state, that's what got recorded in the 
registry and would account for the message.