Re: split packages

[Sven LUTHER <luther@maxime.u-strasbg.fr>]

On Fri, Jun 04, 1999 at 12:03:15AM +1000, Hamish Moffatt wrote:
> On Thu, Jun 03, 1999 at 09:30:43AM -0400, shaleh@clifford.livenet.net wrote:
> > > On Thu, Jun 03, 1999 at 09:13:38AM -0400, shaleh@clifford.livenet.net wrote:
> > > > > But I figure the extra packages are going to be hassle for porters.
> > > > > It seems likely that all three will be released together upstream.
> > > > > Building gschem will need libgeda2, libgeda-dev and geda-symbols installed.
> > > > > This looks like trouble for porters/autobuild daemons. 
> > > > 
> > > > Why can't you set it so that it builds the libs, then compiles the gschem w/
> > > > -L/path/to/my/new/libs and -I/path/to/my/new/headers??
> > > 
> > > Because then you have to have more than one source package unpacked at
> > > once, which the build daemons can do, but it's not the prefered way.
> > > 
> > 
> > Did I misunderstand you Homish?  All three items will be in one source, but one
> > of the items must be compiled after the other two is how I read it.
> 
> Upstream is providing them as three separate sources -- that's the problem,
> since built versions of geda-symbols and libgeda2 will be needed to
> build gschem.

You need source dependencies ...

While you wait for them beign implemented, best would be to packages all this stuff
as only one source package, as before.

Friendly,

Sven LUTHER