Dave,
Could you look at the current fftw.info and grace.info in unstable
and make some suggestions? The problem that the Provides was meant to
solve was the following. If one does "fink install grace" it will
automatically install fftw. However without the Provides: fftw-shlibs
added to fftw.info, "fink install fftw-mpi" will fail afterwards. This
is because grace doesn't know that fftw-mpi-shlibs can satisfy its
fftw-shlibs Depends. The idea was to put the burden of solving this
problem on the fftw.info rather than requiring every single package
that uses fftw to change from...
Depends: fftw-shlibs
...to...
Depends: fftw-shlibs|fftw-mpi-shlibs
The only other option would be to break out fftw-mpi as an add-on package
to fftw. However that would introduce its own issues. For example if
one made fftw-mpi/fftw-mpi-shlibs just contain the additional mpi specific
files, how do you sync it with fftw. For instance, lets say that we
do a 'fink install fftw' with Xcode 1.2 installed and then later upgrade
to Xcode 1.5 before we do a 'fink install fftw-mpi'. Having split the
package, I worried that the shared libs installed in the original build
of fftw against Xcode 1.2 might have different internal symbols than one
one that would be built and linked with against Xcode 1.5 when the mpi
specific libraries are built later. That is I worried about breaking up
the build of fftw and fftw-mpi into two separate sections that might
use different devtools and have different internal symbols.
Jack
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
