Re: [Pkg-grass-general] splitting (from Radim)
On Mon, Oct 11, 2004 at 08:00:19PM +0200, Paolo Cavallini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> This is the advice from Radim Blazek.
> Hope this helps.
> All the best.
> pc
>
> - ---------- Forwarded message ----------
>
> This is question for Glynn, I think, send it to devel list.
>
> I think that now it is possible, but not optimal. I dont quite
> understand
> "first one is just meant to build the development packages
> (libgrass-dev) and doesn't create any binary packages at all."
>
> GDAL depends on libgrass_I, libgrass_vask, libgrass_gmath,
> libgrass_gis and libgrass_datetime but libgrass_vect
> depends on GDAL, so it is impossible to put all GRASS libraries
> to one package.
> It will become even worse once I write OGR driver for GRASS.
>
> Another bad solution could be to built also static libraries
> for GRASS and compile GDAL using static libraries.
>
I'm more and more thinking that the only decent option is to
compile the whole beast together, using one grass+gdal source.
It will produce both libgdal and grass packages...
I'm quite annoyed but this weird thing of building up packages
with recursive depencies anyway, it's typically the symptom
of something wrong in their architecture :-/
The right thing to do is having a third piece of software
and both grass and gdal dependent on it. And this should
be assumed upstream. Other approaches will sooner or later
cause big headaches...
--
Francesco P. Lovergine
Reply to: