Bug#1052224: ITP: libalien-base-modulebuild-perl -- subclass of Module::Build for building Alien:: modules and their libraries

["Francesco P. Lovergine" <frankie@debian.org>]

On Tue, Sep 19, 2023 at 06:36:13PM +0200, Francesco P. Lovergine wrote:
> On Tue, Sep 19, 2023 at 06:13:09PM +0200, gregor herrmann wrote:
> > I can't really test now, because Geo::GDAL::FFI also needs the
> > unpackaged FFI::Platypus::Declare, but from reading
> > https://metacpan.org/release/AJOLMA/Geo-GDAL-FFI-0.1/source/Makefile.PL
> > and
> > https://metacpan.org/release/AJOLMA/Geo-GDAL-FFI-0.1/source/README.md
> > a simple
> >
> > override_dh_auto_configure:
> >   dh_auto_configure -- GDAL=/usr
> >
> > plus build dependencies on gdal-bin (for /usr/bin/gdalinfo) and libgdal-dev
> > might be enough without any Alien::gdal. Maybe :)
> >
> > (Not sure about
> > https://metacpan.org/release/AJOLMA/Geo-GDAL-FFI-0.1/source/lib/Geo/GDAL/FFI.pm#L1567
> > but this is also guarded by an if())
>
> Mmmm, let me see. The chain I used was to impact minimally on changes for the module
> taken from CPAN. I would be happy to minimize the use of all that stuff, I was not exactly
> enthusiastic about the new course at the time.

Ok, it seems that the solution is much more easy than the prospected. The implementation is smart
enough to keep the gdal.so in the right place, something I oversight before. The resulting 
package needs to be arch:any to create a correct internal Geo::GDAL::gdal.pm module per arch,
but it seems working. That said, I would try to patch to avoid the Platypus::Declare use
which is currently discouraged/deprecated: I would avoid to read other complains by gregor :-D

Thanks a lot for the hints.


--
Francesco P. Lovergine