Tim Jenness <[log in to unmask]> writes:
> I don't know whether any of the local debian patches should be moved upstream
> or if they are simply issues with the build system (starlink patches Autoconf
> to support fortran properly).
The patches I apply are:
* rename_library: "pal/ast" (or "PAL/AST") is too short to be accepted
as a package name for such a specific field in Debian --> renamed it
to "starlink-pal". This is probably not to be applied upstream (guess
you like the short names), but since a similar problem (namespace
pollution) will appear in all Linux distributions, it may applicable
to Fedora as well. If you would add something like a "library-prefix"
to configure.ac (which is empty by default, but may be set to
"starlink-" if one wants to avoid namespace problems), I would not
need this patch anymore.
* use_external_pal (AST package): to use PAL as external package with
the changed name, I also need to specify a changed name here. This
could also be solved by an extending the --external-pal option to
specify the library: "--external-pal=-lstarlink_pal".
* use_std_automake: Since Debian doesn't have the full starlink-patched
automake available, but we want to rebuild everything from scratch
(including the invocation of autoreconf), I need to patch the files
configure.ac & Co. The patches do not only contain some Fortran
support, but mainly tests for the other starlink infrastructure
(documentation, starlink utilities). It would be nice to have a
automake files available upstream that support both the starlink and
the standard automake, but I can live with my patches as well. Fedora
will, however, run into the same problem (as long as they are not
going to package the fill startlink ecosystem).
Best regards
Ole
|