i'm asking for a clarification/suggestions here before filling in an
exception request at https://fedorahosted.org/fpc.
I'm packaging a python software called gpaw:
During the tests in %check gpaw uses some static xml and python pckl
data (these are definitions related to chemical symbols).
The data (gpaw-setups) belongs to gpaw (see
and gpaw won't run without it, however gpaw and gpaw-setups are
versioned separately, and therefore
they need to be packaged separately (two separate spec files).
gpaw-setups are being packaged here
I'm asked by the reviewer to remove gpaw-setups bundling from gpaw.
Does the concept of bundling apply to this case?
The problem is that each gpaw release requires a specific release of
gpaw-setups in order for the gpaw tests to pass.
It may happen that new gpaw-setups are released without a new gpaw release.
If the gpaw-setups corresponding to the gpaw release are not bundled in
gpaw one won't be able to run %check during a rebuild of gpaw.
gpaw-setups are bundled in gpaw.spec only for the purpose of %check.
I have a package (compat-qpid-cpp) to be reviewed. Anybody want to swap
Darryl L. Pierce <mcpierce(a)gmail.com>
Famous last words:
"I wonder what happens if we do it this way?"
Packaging (and mpi folks as they are the main users of modules) -
In addition to the current environment-modules package in Fedora,
there is at least one other implementation of the "environment modules"
system - Lmod. This is Lua based rather than C/TCL based but can handle
the TCL based module file format as well as a lua based format with a
.lua extension. There is also the pure TCL version of
environment-modules which some seem to prefer.
I'd like to package Lmod for Fedora as well. My current plan is to
use alternatives for the /etc/profile.d/modules.* links in order to
allow both to coexist. I think we also want to move the current
/usr/share/Modules/modulefiles system module file location to
/usr/share/modulefiles (which would be owned by both environment-modules
and Lmod). That way either package can make use of the modulefiles
installed by other packages. environment-modules currently ships some
sample modules which I'm not yet sure should stay in
/usr/share/Modules/modulefiles (and only be used by it) or if they
should get moved to /usr/share/modulefiles for Lmod's use as well (some
are generic, some specific to environment-modules)
We also would need some kind of virtual provide I believe for module
using packages to require instead of the current "environment-modules".
Perhaps environment-modules(system) or environment(modules)?
Any other comments?
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com