Your message dated Mon, 8 Jun 2009 10:20:30 +0200
with message-id <20090608082030.gb4...@mithrandir>
and subject line [[email protected]: Bug 1534 HDF5 library names]
has caused the Debian Bug report #521221,
regarding libhdf5-openmpi-1.6.6-0: simultaneous installation of -serial and
-mpi packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
521221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521221
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libhdf5-openmpi-1.6.6-0
Version: 1.6.6-4
Severity: wishlist
===============================================
Consider simultaneous installation of serial and parallelized (-mpi) packages.
So the needed
library will be choosen by the application. This will give more flexibility as
applications
that need the serial version can abe installed on the same system with
applications that
need the -mpi version. (Similar as has been done by libgpiv3 and libgpiv-mpi3.)
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages libhdf5-openmpi-1.6.6-0 depends on:
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libopenmpi1 1.3-2 high performance message passing l
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
libhdf5-openmpi-1.6.6-0 recommends no packages.
libhdf5-openmpi-1.6.6-0 suggests no packages.
--- End Message ---
--- Begin Message ---
tags 521221 + wontfix
tags 521221 + upstream
thanks
FYI, if anyone is able to push a different approach to HDF group
this could be fixed. It is a non sense fixing this in debian only
because we would loose source compatibility with upstream.
----- Forwarded message from [email protected] -----
Date: Fri, 5 Jun 2009 12:38:36 -0500 (CDT)
From: [email protected]
To: [email protected]
Subject: Bug 1534 HDF5 library names
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
Hello Mr. Lovergine,
Thank you for your suggestion. We have looked into using
suffix to distinguish different configurations of HDF5
libraries but decided against it due to three concerns:
1. This would require the HDF5 library users to maintain different
versions of autoconfigure and/or Makefiles. This is a
minor concern.
2. A more major one is that HDF5 can have several different
configurations on many big platforms. E.g.,
Due to the big diversity of users in those big platforms,
the System Admin may have built and installed multiple
variations of the same HDF5 release:
a. with or without MPI parallel support;
b. 32bit or 64 bits OS support (e.g., AIX, SunOS, ...);
c. different compilers like Gcc, Intel, or PGI vendors;
d. different versions of the same compilers (e.g., gcc 4.2, 4.3);
e. with or without some HDF5 supported compression features;
In those platforms, the admin usually installs the binaries
of each variation in a separated directory. E.g.,
/usr/apps/hdf5/v1.8.3_gcc4.2_mpich2_107/{bin,lib,include}
/usr/apps/hdf5/v1.8.3_Intel10.1/{bin,lib,include}
...
3. Lastly, a critical concern is that we need to deal with the
HDF5 header files too. The header files of an MPI-Supported
HDF5 built are different in contents from a serial-only HDF5
built. They cannot be installed in the same directory. If
we were to rename the header files with different suffixes,
it would make HDF5 application source code files much more
complex.
Therefore, we have chosen to stay with the same name for the HDF5
library and header files. but rely on other software loading
tools such as "module" to help the users to pick and choose
their own flavors of HDF5 libraries.
We recognize that this is not the perfect solution for everyone
in all situations but we feel this is a good compromise for our
users.
========
> From Francesco P. Lovergine
...
* MPI flavors use the same names of serial libraries, which prevents installing
and using both serial and MPI flavors of the libraries on the same system.
Other libraries provide a _mpi suffixes for MPI-enabled libraries to allow
that.
=========
----- End forwarded message -----
--
Francesco P. Lovergine
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
