[Bug 167253] Review Request: CERN library and associated binaries

[bugzilla redhat com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: CERN library and associated binaries


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167253





------- Additional Comments From pertusus free fr  2005-08-31 18:24 EST -------
This is a very big package and I have a few comments.

I used lots of things from the debian packages. There are a lot of information
at the cernlib on debian faq page: 
http://borex.princeton.edu/~kmccarty/faq.html

The debian patches allowing for dynamic libraries creation haven't been applied. 

The cernlib almost build with gfortran but still fails because of unimplemented
f2c intrinsics. Patches to build with gortran are included and applied anyway.

Patches that solved security issues that have been applied in the previous
cernlib release have been kept, to help people packaging the previous release if
they want to.

The libraries should be parallel installable with each years release, and I
think this is a important feature for some potential users of the cernlib that
relies on older and stable software  still being available. 

The helper build scripts are not paralell installable so I added them to a
separate package I called cernlib-utils. rpmlint complains about that package
depending on a devel package but it seems right to me. It also give
E: cernlib-utils script-without-shellbang /etc/profile.d/cernlib-2005.sh
but the other scripts in /etc/profile.d/ don't have shellbangs.

The source doesn't match the upstream source for some tarballs, as files with
licences incompatible with the GPL are removed. See the debian files for more
information and the comments in the specfile on how to regenerate the modified
sources.

More information in the included cernlib.README 

 

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.