Date: Mon, 6 Feb 2017 09:51:36 +0100 From: =?UTF-8?Q?Ren=C3=A9_Ladan?= <r.c.ladan@gmail.com> To: Rainer Hurling <rhurlin@gwdg.de> Cc: Kurt Jaeger <lists@opsec.eu>, Don Zavitz <don@zavitz.ca>, freebsd ports <freebsd-ports@freebsd.org> Subject: Re: devel/libcheck Message-ID: <CADL2u4g6m-wC2UGUGpFq19MNGvEgM=h3%2BrdKHNArbDnDRLMpJQ@mail.gmail.com> In-Reply-To: <49464a20-dfd7-302e-4890-5e4dd6f5cf15@gwdg.de> References: <3df61113-0150-d487-a32b-7041d5ebd99f@zavitz.ca> <20170206062916.GE13006@home.opsec.eu> <49464a20-dfd7-302e-4890-5e4dd6f5cf15@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
2017-02-06 9:18 GMT+01:00 Rainer Hurling <rhurlin@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 t= o figure this out from MOVED (which is mostly meant for machines). Ren=C3=A9 --=20 https://rene-ladan.nl/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADL2u4g6m-wC2UGUGpFq19MNGvEgM=h3%2BrdKHNArbDnDRLMpJQ>