devel/libcheck

[Rainer Hurling]

Hi René,

Am 06.02.2017 um 09:51 schrieb René Ladan:
> 2017-02-06 9:18 GMT+01:00 Rainer Hurling <rhurlin at gwdg.de
> <mailto:rhurlin at gwdg.de>>:
> 
>     Am 06.02.2017 um 07:29 schrieb Kurt Jaeger:
>     > Hi!
>     >
>     >> I just went to update my ports today on a machine, and there was a
>     >> conflict between devel/check and devel/libcheck.
>     >
>     > It's more that libcheck was moved to check.
>     >
>     > According to /usr/ports/MOVED:
>     >
>     > devel/libcheck|devel/check|2017-02-05|Rename to match upstream naming
>     >
> 
>     For me, the following did the job:
> 
>         portmaster -o devel/check libcheck-0.10.0
> 
>     Perhaps, this is something for UPDATING?
> 
> No, UPDATING is for things humans need to do. portmaster should be able
> to figure this out from MOVED (which is mostly meant for machines).

Of course, I know this about UPDATING.

In this case with devel/check, the automatism with portmaster does not
work as expected, at least for Don and me.

Shouldn't portmaster, after a successful build of devel/check, first
deinstall libcheck and than install check?

For some reason, this seems not to work as expected. When portmaster
tries to install devel/check, it conflicts with a present
/usr/local/bin/checkmk, because libcheck was not uninstalled before.

I have no clue about the underlying reasons.

Rainer

> 
> René
> -- 
> https://rene-ladan.nl/