[Pkg-scicomp-devel] anyone packaging Framewave?

[Albert Huang]

Ok, this is fixed upstream now but not yet formally released.  I've
modified the package to build from framewave subversion, similar to
how ffmpeg is packaged.

One question I'm not sure about is whether to keep framewave as two
binary packages (libfwbase1, libfwbase1-dev) or eight -- two for each
library (libfwbase1, libfwimage1, libfwvideo, etc).  For now I've
packaged them all together as libfwbase1, libfwbase1-dev because I
don't think many people will have much use for them as separate
packages.

-albert

On Wed, Apr 9, 2008 at 4:21 PM, Albert Huang <ashuang at gmail.com> wrote:
> Hi Christophe,
>
>  Ok, I will let you know when it's fixed.  The build also fails for me
>  at the same place -- some of the -I flags are missing a leading '/'
>  and so what should be an absolute path turns into a relative path.
>
>  In the past, I've used the svn-bp:origUrl property in the debian/
>  directory to direct svn-buildpackage on where to find the upstream
>  tarball.  Do you prefer having an explicit rule for doing this in the
>  rules file?
>
>  -albert
>
>
>
>  On Tue, Apr 8, 2008 at 4:00 AM, Christophe Prud'homme
>  <prudhomm at debian.org> wrote:
>  > Ok let me know how it goes