Date: Tue, 25 Nov 2014 14:56:28 +0000 From: Gary Palmer <gpalmer@freebsd.org> To: Andrew Berg <aberg010@my.hennepintech.edu> Cc: freebsd-multimedia@freebsd.org, freebsd-ports@freebsd.org Subject: Re: [SOLVED] multimedia/x264 build failure, linker error Message-ID: <20141125145628.GB24514@in-addr.com> In-Reply-To: <547493A0.70001@my.hennepintech.edu> References: <2002873.iA6NuqLZfy@amd.asgard.uk> <2718486.HeFL0Qyace@amd.asgard.uk> <24936541.dtFOE5QvMi@amd.asgard.uk> <20141124223344.GA9356@pcjas.obspm.fr> <CAN6yY1sMv3Ok4U3s9P6as%2BB4CgYChR1kAAteZiG4bRkPxa3c8Q@mail.gmail.com> <20141125142631.GA24514@in-addr.com> <547493A0.70001@my.hennepintech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 25, 2014 at 08:35:12AM -0600, Andrew Berg wrote: > On 2014.11.25 08:26, Gary Palmer wrote: > > Since I assume most of the packages that depend on the old x264-0.136.2358_4 > > depend on the library rather than the CLI command, is there any harm in > > doing > > > > portmaster -o multimedia/libx264 x264-0.136.2358_4 > > > > instead? That way the dependancies are kept (mostly) correct > Don't do that. The dependency change has been properly handled, and those ports > know to use multimedia/libx264. If you followed the instructions in the mail I replied to, the installed packages are left with a dependency on x264 and not libx264. The real problem is that the few times I tried to use automated update methods ran into problems because x264 was already installed and libx264 couldn't be installed because they conflicted. Nothing seems to be in UPDATING or MOVED so the upgrades break. There needs to be a better way of handling these cases. Regards, Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141125145628.GB24514>