ITP: python-gpiv -- wrapper of libgpiv

2008-12-05 Thread Gerber van der Graaf
* Package name: python-gpiv
  Version : 1.0.0
  Upstream Author : Name <[EMAIL PROTECTED]>
* URL : http://libgpiv.sourceforge.net/pygpiv.html
* License : GPL
  Programming Lang: Python
  Description : wrapper of libgpiv

This module allows the functionality of libgpiv in Python scripts
to quick develop programs for Particle Image Velocimetry (PIV).

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



ITP: python-gpiv -- wrapper of libgpiv

2008-12-05 Thread Gerber van der Graaf
Package : python-gpiv
Version : 1.0.0
Upstream Author : Name <[EMAIL PROTECTED]>
URL : http://libgpiv.sourceforge.net/pygpiv.html
License : GPL
Programming Lang: Python
Description : wrapper of libgpiv

This module allows the functionality of libgpiv in Python scripts
to quick develop programs for Particle Image Velocimetry (PIV).

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#507894: ITP: python-gpiv -- wrapper of libgpiv

2008-12-05 Thread Gerber van der Graaf
Package: wnpp
Severity: wishlist
Owner: Gerber van der Graaf <[EMAIL PROTECTED]>


* Package name: python-gpiv
  Version : 1.0.0
  Upstream Author : Gerber van der Graaf <[EMAIL PROTECTED]>
* URL : http://libgpiv.sourceforge.net/pygpiv.html
* License : GPL
  Programming Lang: Python
  Description : wrapper of libgpiv

This module allows the functionality of libgpiv in Python scripts
to quick develop programs for Particle Image Velocimetry (PIV).

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#507895: ITP: python-gpiv -- wrapper of libgpiv

2008-12-05 Thread Gerber van der Graaf
Package: wnpp
Severity: wishlist
Owner: Gerber van der Graaf <[EMAIL PROTECTED]>


* Package name: python-gpiv
  Version : 1.0.0
  Upstream Author : Gerber van der Graaf <[EMAIL PROTECTED]>
* URL : http://libgpiv.sourceforge.net/pygpiv.html
* License : GPL
  Programming Lang: Python
  Description : wrapper of libgpiv

This module allows the functionality of libgpiv in Python scripts
to quick develop programs for Particle Image Velocimetry (PIV).

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#515789: ITP: mgridgen(-mpi) -- Program for generating course grids

2009-02-17 Thread Gerber van der Graaf
Package: wnpp
Severity: wishlist
Owner: Gerber van der Graaf 


* Package name: mgridgen(-mpi)
  Version : 1.0.0
  Upstream Author : Irene Moulitsas 
* URL : http://www.cs.umn.edu/~moulitsa/software.html
* License : (Unspecified, I will contact upstream authors for (GNU) 
licence agreement and permission of distribution in Debian)
  Programming Lang: (C)
  Description : Program for generating course grids

MGRIDGEN and PARMGRIDGEN are serial and parallel software packages that 
implement various algorithms for
generating a sequence of coarse grids. The generated coarse grids contain 
well-shaped elements and thus they are
well-suited for geometric multigrid methods. PARMGRIDGEN is an MPI-based 
parallel library that is based on the
serial package MGRIDGEN and it is suited for parallel numerical simulations 
involving large unstructured grids since
the algorithms incur a very small communication overhead, achieve high degree 
of concurrency and maintain the high
quality of the coarse grids obtained by the serial algorithms in the MGRIDGEN 
library.


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: simultaneous installation lib and lib-mpi

2009-04-30 Thread Gerber van der Graaf
A start has been made already some time ago with this. See Debian bug
#521221 libhdf5-openmpi-1.6.6-0: simultaneous installation of -serial
and -mpi packages

Gerber


On Thu, 2009-04-30 at 10:11 +0200, Francesco P. Lovergine wrote:
> On Sun, Apr 26, 2009 at 08:19:20PM +0200, Magnus Holmgren wrote:
> > On torsdagen den 26 februari 2009, Gerber van der Graaf wrote:
> > > I came across this problem when packaging my own libgpiv3 / libgpiv-mpi3
> > > (recently accepted and uploaded). These libraries are used by the other
> > > packages gpivtools / gpivtools-mpi from a single upstream source (not
> > > yet available on Deb). When testing the packaging of gpivtools(-mpi)
> > > with pbuilder it only can be done if libgpiv3 and libgpiv-mpi3 are to be
> > > installed simultaneously. Otherwise the building of one of the packages
> > > gpivtools / gpivtools-mpi is impossible.
> > >
> > > While working on the packaging of gpivtools(-mpi) I am getting across a
> > > similar problem with other libraries that are available in seriel and
> > > -mpi (libhdf5-serial-dev libhdf5-openmpi-dev to be more specific). Only
> > > one of these can be installed at once. As I also work with Paraview,
> > > which depends on libhdf5-openmpi, packaging and the use of gpivtools
> > > (that depends on libhdf5-dev) is impossible. (It is preferred to have
> > > the dependancy on libhdf5-dev, even in gpivtools-mpi as the .h5 files
> > > are quite small and don't need to be stored/retrieved in parallel way.)
> > >
> > > My question is why isn't it possible to package such libraries in a way
> > > they can be installed simultaneously? Am I doing something wrong here?
> > > If not, a suggestion might be to provide this possibility by filing a
> > > 'feature request' bug against all -mpi libraries. If this really is a
> > > weak point in packaging such libs, shouldn't it become a formal
> > > packaging policy?
> > 
> > There are more examples, such as cyrus-sasl2, which contains two Kerberos 
> > GSSAPI modules, one using MIT Kerberos 5 and one using Heimdal. But because 
> > those libraries can't be installed simultaneously, there is a separate 
> > source 
> > package, cyrus-sasl2-heimdal, with a copy of the upstream tarball, which 
> > only 
> > builds the Heimdal module packages. Currently I don't think there is any 
> > other solution to this problem, and solving it "for real" would require 
> > rather serious changes to how packages are built, but it might still be 
> > meaningful to bring it up on -devel, which I've done now.
> > 
> 
> The best reasonable solution is convincing upstream to build rather different
> lib names and sonames for each case. That would imply that all people
> depending on the mpi lib flavor should change their library names. Providing
> the same kind of implementation in our distribution is a viable possibility,
> but diverged by upstream: that should be done in the library package, while
> the serial and mpi -dev packages still should retain the same names (and
> conflict each other). This is what I will implement for the HDF5 case.
> 
> -- 
> Francesco P. Lovergine
> 
> 


signature.asc
Description: This is a digitally signed message part


Bug#528662: ITP: freefoam -- freefoam software package for Computational Fluid Dynamics (CFD).

2009-05-14 Thread Gerber van der Graaf
Package: wnpp
Severity: wishlist
Owner: Gerber van der Graaf 


* Package name: freefoam
  Version : 0.1.0
  Upstream Author : Michael Wild 
* URL : http://www.freefoam.wiki.sourceforge.net
* License : GPL
  Programming Lang: C++
  Description : software for Computational Fluid Dynamics (CFD)

FreeFOAM is a fork of the OpenFOAM CFD software package, containing more than 
200 programs for pre-processing, simulation and for post-processing. Therefore 
it uses the control volume method or finite difference scheme. The software can
simulate anything from complex fluid flows involving chemical reactions, 
turbulence and heat transfer, to solid dynamics, electromagnetics and the 
pricing of financial options.
..
Compared to OpenFOAM, the building system has been 
modified to CMake, will also compile and run on case-insensitive file systems
and installs configuration, libraries, headers and binaries following LSB 
standards. 
Its use won´ require specific ENVIRONMENTAL settings or has been reduced to a
minimum. So all programs will work like any other available binary on the 
Computer system.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org