dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Sun, Jul 17, 2005 at 06:21:46PM -0400, Faheem Mitha wrote:
> 
> 
> On Sun, 17 Jul 2005, Anders Logg wrote:
> 
> >On Sun, Jul 17, 2005 at 03:02:53AM -0400, Faheem Mitha wrote:
> 
> >As I understand it, Debhelper is only a requirement for you to build
> >the DOLFIN package, not for a user who installs it so it should not be
> >a requirement. Right?
> 
> It is not a Depends (runtime) but is a BuildDepend (build time), which is 
> quite common.

ok, I wasn't aware of this distinction.

> >>Ok. I'll hold off on packaging FFC and FIAT till later.
> >
> >Should be very easy to package. The only thing that needs to happen is
> >a to copy a bunch of .py files to
> >
> >   /usr/lib/python-<version>/site-packages/<name>
> >
> >which is what happens when you run
> >
> >   python setup.py install
> >
> >in FFC or FIAT (Python standard correpsonding to ./configure + make).
> >
> >But this can wait.
> 
> I'll take a look at it when I have a chance. I think Debian Python policy 
> expects certain things, so it will not be quite so trivial.

Probably not...

> >>libpetsc is too big. Please suggest how its size could be reduced. Also,
> >>do you have any suggestions on how the runtime and dev libraries could be
> >>split up?
> >
> >Seems to be difficult to get around:
> >
> >galerkin:/usr/local/lib/petsc> ls -lh lib/linux-gnu/
> >totalt 157M
> >-rw-r--r--  1 root root  56K 2005-07-04 06:06 libmpiuni.a
> >-rw-r--r--  1 root root  33M 2005-07-04 06:06 libpetsc.a
> >-rw-r--r--  1 root root  11M 2005-07-04 06:06 libpetscdm.a
> >-rw-r--r--  1 root root  38M 2005-07-04 06:06 libpetscfortran.a
> >-rw-r--r--  1 root root  20M 2005-07-04 06:06 libpetscksp.a
> >-rw-r--r--  1 root root  38M 2005-07-04 06:06 libpetscmat.a
> >-rw-r--r--  1 root root 5,3M 2005-07-04 06:06 libpetscsnes.a
> >-rw-r--r--  1 root root 3,1M 2005-07-04 06:06 libpetscts.a
> >-rw-r--r--  1 root root  11M 2005-07-04 06:06 libpetscvec.a
> 
> Hmm. The library files in my PETSc package aren't quite that big. Maybe 
> because they are stripped? In any case, we can split the library files up 
> into subpackages, which will help.
>
> I wonder how Powell managed. Should look at his package.
> 
>                                                               Faheem.

Powell's package is surprisingly small so he must have done something
clever.

/Anders