On 06/01/2018 19:38, William Harrington wrote: > On Sat, 6 Jan 2018 19:16:15 +0100 > Pierre Labastie <[email protected]> wrote: > >> Note that solving >> the freetype<->harfbuzz cycle is slightly more complicated: you have to tell >> the system that freetype should be built *both* before and after harfbuzz, >> but >> the "before" one does not depend on harfbuzz... > > Hello, > > With my modified jHALFS builds I end up having three targets: > > freetype, harfbuzz, freetype-harfbuzz > > Build freetype, first. > Build harfbuzz, second. > Build freetype after harfbuzz. > > The only downfall with that is I had to link freetype-harfbuzz-2.8.1.tar.bz2 > to freetype-2.8.1.tar.bz2 and adjust pkg_tarball_list. > > Same for iptables and nftables. > iptables, nftables, iptables-nftables >
Normally, with the current way script file names are generated (ddd-z-scriptname), I usually get something like (numbers are taken from a real case): 011-z-freetype2 012-z-harfbuzz 013-z-fontconfig. I just do "cp 011-z-freetype2 013-y-freetype2". The problem is to automate this... With "modified jHALFS builds", do you mean you got some automation? If so, I'd be very interested in knowing details. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
