Description of problem:
There is no way to find cernlib.
I have a package that needs cernlib (and cernlib-devel) This package uses
autoconf for building. I have to
I think including cernlib/cernlib-static py scripts mentioned in cernlib.ac
should be installed with cernlib. Otherwise it is impossible to write new spec
files for packages using cernlib without hardcoding the version or doing some
other ugly hack.
Version-Release number of selected component (if applicable):
The script is in cernlib-utils. I tried to keep the possibility
of installing cernlib(-devel) 2005 and cernlib(-deve) 200x side by side,
so the cernlib and cernlib-static scripts which are version dependent
(for the default year) are not in the -devel package, but in the
-utils subpackage. (as a side note, the cernlib.m4 macro is not
version specific, but it may be arguable that it shoule better be in
the -utils package).
Seems like the cern dropped the cernlib, so it seems that there won't
be any new cernlib version, but who knows...
Is it satisfying? I am open to other advices on how to package
I don't know :(
It's a good idea to keep the possibility of installing different versions of
cernlib. It's also good that the version dependent stuff is in a separate
package. So I guess you did the best given the mess cernlib is.
btw have you noticed cernlib 2006 was available?
(In reply to comment #3)
> btw have you noticed cernlib 2006 was available?
No I hadn't noticed, thanks for the info. The debian maintainer
wasn't noticed either. Some of the differences are similar with
what is in the debian patch, but not exactly the same, and for
a difference I spotted what is upstream is wrong :-(. I really
can't understand why they cannot coordinate with the cernlib
versions shipped in major distros. Anyway the debian maintainer
is now working at merging the patchesets, I will use what comes
out. The other change is the support of svg in graphlib, and
merging of the sources. The license violations aren't corrected.
I am not convinced that it is really worth keeping a 2005
compatibility library (as a side note once it builds with gfortran
it could be worth having a library compiled with g77).
I have updated the to cernlib-2006 version. I won't keep a
cernlib 2005 around because they are very similar, however
now that the cernlib-2006 is compiled with gfortran I
for the cernlib compiled with g77.
I close this bug.