On Wed, 12 Feb 2014 10:05:41 -0800 "Schlacta, Christ" <aarc...@aarcane.org> wrote:
> So I'm working on backporting enlightenment e17 from jessie to wheezy > since my request to backports went unanswered. Anyway, I believe I've > found out why. > > Enlightenment is comprised of about a dozen packages, each of which > depends on the previous having been built and installed beforehand. > And none of them are in wheezy by default. > > I've had mostly success so far, but I hope to get the process mostly > automated using pbuilder. That's where I'm stuck. > > I don't know how to handle this complex dependency of each package on > previous packages in the complex build process Keep building all packages in a loop, remove the package from the loop when it has been built, repeat. The order of the loop barely matters. The problems are that programs are build-dependencies of libraries which have -dev packages which are build-dependencies of programs. There are tools which can identify dependency loops, but for a single run, it is just as effective to try everything, rebuild everything which broke and repeat, repeat, repeat. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
