On Mon, May 08, 2017 at 05:45:09PM +0000, Carsten Mattner via arch-general wrote: > On Sun, May 7, 2017 at 6:37 PM, Eli Schwartz via arch-general > <arch-general@xxxxxxxxxxxxx> wrote: > > On 05/07/2017 02:28 PM, Carsten Mattner via arch-general wrote: > >> On Sun, May 7, 2017 at 6:11 PM, Doug Newgard <scimmia@xxxxxxxxxxxxxx> wrote: > >>> And again, the cycle doesn't matter at all if your ffmpeg package is set up > >>> correctly. > >> > >> I don't understand how I can without additionally repacking libx264/x264, > >> but hopefully I will see what you're saying later today or tomorrow. > > > > What Doug is saying is, you should do what 99.9999999% of all other Arch > > Linux users creating custom packages to replace repo packages do, and > > make your forked ffmpeg package provide "ffmpeg", thereby ensuring that > > libx264/x264 depend on *your* package! > > Is the idea that I create a machine local repo that has highest prio > and overrides arch extra/testing? Otherwise, I don't know how to unbreak > the cycle while only building a custom ffmpeg. I don't understand... testing/libx264 contains /usr/include/x264.h and doesn't depend on ffmpeg, no? Cheers, -- Leonid Isaev
