On Tue, 09 Apr 2019 10:27:32 +0200
Bas Couwenberg <[email protected]> wrote:
> On 2019-04-09 10:10, Oliver Eichler wrote:
> >> > make install
> >>
> >> You probably used CMake to build PROJ, the Debian package uses
> >> Autotools
> >> and IIRC the CMake files are only built & installed when using
> >> CMake.
> >>
> >
> > Yes of course I used cmake. Haven't used Autotools for a long time.
> > But regardless of the used build tools shouldn't a distribution
> > package contain everything? Does every project using cmake and PROJ
> > have to maintain it's own reincarnation of the cmake script just
> > because Debian packages are missing it? That does not sound very
> > sane to me.
>
> It's not just the Debian package, it all PROJ packages that use
> Autotools this includes at least Fedora & NetBSD.
>
> Ideally the result of the CMake and Autotools builds is identical,
> but this is hard to achieve. Projects that support both tend to have
> CMake support for Windows mostly.
>
> >> > /usr/share/cmake/Modules/FindQuaZip5.cmake
> >> >
> >> > Is it possible that Debian development packages aren't complete?
> >>
> >> libquazip5-dev does provide the file, but it's not installed in the
> >> standard CMake modules path:
> >>
> >> /usr/share/quazip/FindQuaZip5.cmake
> >>
> >
> > Well I am not that much of a package and Linux guru but if I have a
> > look at /usr/share/cmake/Modules/ I find loads of find scripts. I
> > can't tell if that is because many packages think this is the
> > correct path or because the SuSE maintainers simply do it that way.
> >
> > Anyway I think it's good practice to take stuff that is the same for
> > each project away from projects. And maintaining a reincarnation of
> > a cmake configuration script is such stuff for sure. These cmake
> > scripts in QMS had their origin from times where most projects like
> > PROJ where not aware of cmake. But this is about 10 years ago and
> > meanwhile most projects provide these files.
> >
> > Thus wouldn't it be better to take them over in the packages?
>
> In Debian the standard CMakes file are in
> /usr/share/cmake-<VERSION_MARJOR>.<VERSION_MINOR>/Modules/ which
> means that packages need to be rebuilt for every new CMake minor
> release to install their CMake files in the versioned directory.
>
> In my opinion you can only rely on modules included in CMake itself,
> anything else should be included in QMS for robustness sake.
>
> So just apply my patches and everyone not on OpenSUSE is happy that
> they can build QMS out-of-the box again.
I haven't chance to try the new QMS release with Fedora yet, but in
general the value of distribution is in the integration and providing a
common developer experience. So if upstream doesn't install the cmake
snippet (but it's included) or puts it in a non-standard location, then
it's the packager's job to fix that. The problem with bundled stuff
(like the cmake snippets in QMS) is that it gets outdated easily, etc.
With regards,
Dan
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
