Re: Need advice on building a package

On Wed, Feb 12, 2014 at 2:51 PM, John Holland <jholland@vin-dit.org> wrote:

I got some debs built for E 18 not 17 gby oing from the source on
enlightenment.org and building them on Wheezy. They've been working
pretty well for me on a couple machines.

Thank you for the suggestion, but I'm strictly attempting to stick to backporting packages from Jessie to maintain upgradability later.

You might want to look at the E18 situation because many of the
dependencies for E17 have been combined into one tarball that will
build them all at once. I had some previous attempts to make E17 debs
and the number of dependencies is pretty overwhelming. E18 made it a
lot easier.

I was a bit dismayed with the extent of the build process :(

I do look forward to E18 making it into Jessie now.

my debs are at www.vin-dit.org (instructions on the web page)

Do you have dscs for building from source?

On Wed, 12 Feb 2014 10:34:54 -0800

"Schlacta, Christ" <aarcane@aarcane.org> wrote:

> On Feb 12, 2014 10:19 AM, "Neil Williams" <codehelp@debian.org> wrote:
> >
> > On Wed, 12 Feb 2014 10:05:41 -0800
> > "Schlacta, Christ" <aarcane@aarcane.org> wrote:
> > >
> > > 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.
> >
>
> That's not quite the problem. Insofar as I can tell, all the
> dependencies form a nice pretty tree.
>
> I just need the output from each package to build the next, and I'm
> looking for an automated way to do that in pbuilder