fftw3 and octave

fftw3 and octave

[Dr. Volker Zell]

Hi

The links to fftw3 and octave redirect to

 o http://it.altervista.org/

without any content.

Some remarks to your package [ITA] [RFU] for fftw3:

The current situation in the distro is:

 fftw3
 fftw3-doc
 fftw3-dev

Given that only octave is using fftw3 I would suggest a splitting like:

 fftw3
 libfftw3_3
 libfftw3-devel
and maybe
 fftw3-doc

instead of your proposal of

 fftw3
 libfftw3-devel
 
so that we have a pure runtime shared library package libfftw3_3 that
other packages can depend on.


For octave the current situation is

 octave
 octave-otags
 octave-info
 octave-htmldoc
 octave-headers
 octave-forge
 octave-doc

Your RFU is for

 octave
 octave-devel

so you should provide empty packages for the rest.

Your RFU states:

  To build the full package I also package the 
  libraries needed to fully compile octave:

  Qhull-2003.1
  Hdf5-1.6.7
  glpk-4.21     (the latest versions does not compile
                  cleanly, so I used this one)
  SuiteSparse-3.1.0

Are these static libraries ? Otherwise your build would depend on them
and you should package them for the distro.

Ciao
  Volker

Re: fftw3 and octave

[Marco Atzeri]

--- "Dr. Volker Zell"  ha scritto:
> Hi
> 
> The links to fftw3 and octave redirect to
> 
>  o http://it.altervista.org/
> 
> without any content.

Hi Volker,
it seems my provider added some type of filter to
avoid download without passing trough the 
web pages.

Please try from here

http://matzeri.altervista.org/cygwin/fftw3/
http://matzeri.altervista.org/cygwin/octave/

> 
> Some remarks to your package [ITA] [RFU] for fftw3:
> 
> The current situation in the distro is:
> 
>  fftw3
>  fftw3-doc
>  fftw3-dev
> 
> Given that only octave is using fftw3 I would
> suggest a splitting like:
> 
>  fftw3
>  libfftw3_3
>  libfftw3-devel
> and maybe
>  fftw3-doc
> 
> instead of your proposal of
> 
>  fftw3
>  libfftw3-devel
>  
> so that we have a pure runtime shared library
> package libfftw3_3 that
> other packages can depend on.

the DLL are almost all the size of fftw3
so I can repakage as suggested, but it is 
probably not worth.

> 
> 
> For octave the current situation is
> 
>  octave
>  octave-otags
>  octave-info
>  octave-htmldoc
>  octave-headers
>  octave-forge
>  octave-doc
> 
> Your RFU is for
> 
>  octave
>  octave-devel
> 
> so you should provide empty packages for the rest.

octave forge is a separate package, that I will
adopt as soon as I complete the packaging.
I will provide the empty packages for the rest.

> 
> Your RFU states:
> 
>   To build the full package I also package the 
>   libraries needed to fully compile octave:
> 
>   Qhull-2003.1
>   Hdf5-1.6.7
>   glpk-4.21     (the latest versions does not
> compile
>                   cleanly, so I used this one)
>   SuiteSparse-3.1.0
> 
> Are these static libraries ? Otherwise your build
> would depend on them
> and you should package them for the distro.

Of course static. 
The only dependency needed was fftw3
so I adopted it. 

> 
> Ciao
>   Volker
> 
Ciao
Marco



      ___________________________________ 
Scopri il Blog di Yahoo! Mail: trucchi, novità, consigli... e la tua opinione!
http://www.ymailblogit.com/blog/

Re: fftw3 and octave

[Charles Wilson]

Marco Atzeri wrote:

> the DLL are almost all the size of fftw3
> so I can repakage as suggested, but it is 
> probably not worth.

Not exactly. The import libraries are almost half the size of the DLLs; 
that's not insignificant. Here's what Volker is suggesting, I think 
(with perhaps a few things moved around). I've put the "basic" 
documentation in libfftw3-devel, and the "fancy, extra" documentation in 
fftw3-doc).  You'll notice that with this division, the size is 
distributed across the packages -- if not evenly, then at least 
'fairly'.  Also, in this scheme, the 'main' package (fftw3, the one 
whose name matches the -src) contains only /usr/share README-style 
stuff. That's a fairly common occurance for DLL utilitity libraries.

libfftw3_3:
520704   /usr/bin/cygfftw3-3.dll
  70656   /usr/bin/cygfftw3_threads-3.dll
------------
591360 TOTAL

libfftw3-devel:
   2202   /usr/bin/fftw-wisdom-to-conf
  34816   /usr/bin/fftw-wisdom.exe
327332   /usr/lib/libfftw3.dll.a
    762   /usr/lib/libfftw3.la
  54536   /usr/lib/libfftw3_threads.dll.a
    815   /usr/lib/libfftw3_threads.la*
    209   /usr/lib/pkgconfig/fftw3.pc
   2143   /usr/include/fftw3.f
  10021   /usr/include/fftw3.h
  51019   /usr/share/info/fftw3.info-1
  51018   /usr/share/info/fftw3.info-2
  44463   /usr/share/info/fftw3.info-3
  43162   /usr/share/info/fftw3.info-4
  11149   /usr/share/info/fftw3.info-5
  1821    /usr/share/info/fftw3.info.gz
  1743    /usr/share/man/man1/fftw-wisdom-to-conf.1.gz
  2975    /usr/share/man/man1/fftw-wisdom.1.gz
------------
640186 TOTAL

fftw3-doc:
498555   /usr/share/doc/fftw3-3.0.1/fftw3.pdf
  30406   /usr/share/doc/fftw3-3.0.1/fftw-faq.ascii
          /usr/share/doc/fftw3-3.0.1/html/*
------------
919597 TOTAL

fftw3:
2121    /usr/share/doc/Cygwin/fftw3-3.0.1.README
173     /usr/share/doc/fftw3-3.0.1/AUTHORS
196103  /usr/share/doc/fftw3-3.0.1/ChangeLog
17992   /usr/share/doc/fftw3-3.0.1/COPYING
821     /usr/share/doc/fftw3-3.0.1/COPYRIGHT
9498    /usr/share/doc/fftw3-3.0.1/INSTALL
5346    /usr/share/doc/fftw3-3.0.1/NEWS
1253    /usr/share/doc/fftw3-3.0.1/README
1615    /usr/share/doc/fftw3-3.0.1/TODO
------------
234922 TOTAL


However, putting the DLLs in a separate, standalone package is not just 
about download size.  It also helps with package and dependency 
management, if the API of the library changes in a 
backwards-incompatible manner.

>> Are these static libraries ? Otherwise your build
>> would depend on them
>> and you should package them for the distro.
> 
> Of course static. 
> The only dependency needed was fftw3
> so I adopted it. 

Not to look a gift horse in the mouth, but cygwin binary software is 
under the GPL (or compatible open source license), because it is linked 
against the cygwin1.dll.

This means that, for ALL software linked into the binaries included in 
the cygwin distribution, we MUST also distribute the source.

Including static libraries.

The most convenient way to ensure this is for all dependent libraries to 
ALSO be members of the cygwin distribution.

So, we usually don't allow software in the distro that links against 
libaries that AREN'T part of the distro -- unless you take special care 
to distribute also those EXACT sources as part of your fftw3-src package.

I'll leave this to Corinna and cgf to decide, but it seems to me that 
either:

(1) you must rebuild your official package without reliance on Qhull, 
Hdf5, and qlpk/SuiteSparse, or
(2) include the EXACT Qhull/Hdf5/qlpk/SuiteSparse source code tarballs 
within the fftw3-src tarball
(3) you [or someone else] must ITP these packages

or else we must continue to go without an octave maintainer.  However, 
that's just MHO, and I'm not in charge.

--
Chuck

Re: fftw3 and octave

[Corinna Vinschen]

On Apr  1 00:02, Charles Wilson wrote:
> Marco Atzeri wrote:
>> Of course static. The only dependency needed was fftw3
>> so I adopted it. 
>
> Not to look a gift horse in the mouth, but cygwin binary software is under 
> the GPL (or compatible open source license), because it is linked against 
> the cygwin1.dll.
>
> This means that, for ALL software linked into the binaries included in the 
> cygwin distribution, we MUST also distribute the source.
>
> Including static libraries.
>
> The most convenient way to ensure this is for all dependent libraries to 
> ALSO be members of the cygwin distribution.
>
> So, we usually don't allow software in the distro that links against 
> libaries that AREN'T part of the distro -- unless you take special care to 
> distribute also those EXACT sources as part of your fftw3-src package.
>
> I'll leave this to Corinna and cgf to decide, but it seems to me that 
> either:
>
> (1) you must rebuild your official package without reliance on Qhull, Hdf5, 
> and qlpk/SuiteSparse, or
> (2) include the EXACT Qhull/Hdf5/qlpk/SuiteSparse source code tarballs 
> within the fftw3-src tarball
> (3) you [or someone else] must ITP these packages

100% correct.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Re: fftw3 and octave

[Marco Atzeri]

--- Corinna Vinschen ha scritto:

> On Apr  1 00:02, Charles Wilson wrote:
> > Marco Atzeri wrote:
> >> Of course static. The only dependency needed was
> fftw3
> >> so I adopted it. 
> >

> > I'll leave this to Corinna and cgf to decide, but
> it seems to me that 
> > either:
> >
> > (1) you must rebuild your official package without
> reliance on Qhull, Hdf5, 
> > and qlpk/SuiteSparse, or
> > (2) include the EXACT Qhull/Hdf5/qlpk/SuiteSparse
> source code tarballs 
> > within the fftw3-src tarball
> > (3) you [or someone else] must ITP these packages
> 
> 100% correct.
> 

I think (3) is more easy, as I already 
built and packaged them. 

http://www.matzeri.altervista.org/cygwin/qhull/
http://www.matzeri.altervista.org/cygwin/hdf5/
http://www.matzeri.altervista.org/cygwin/glpk/
http://www.matzeri.altervista.org/cygwin/suitesparse/

Can we leave them as a monolithic packages ?

> 
> Corinna

Regards
Marco



      ___________________________________ 
Scopri il Blog di Yahoo! Mail: trucchi, novità, consigli... e la tua opinione!
http://www.ymailblogit.com/blog/

Re: fftw3 and octave

[Marco Atzeri]

--- Charles Wilson ha scritto:

> Marco Atzeri wrote:
> 
> > the DLL are almost all the size of fftw3
> > so I can repakage as suggested, but it is 
> > probably not worth.
> 
> Not exactly. The import libraries are almost half
> the size of the DLLs; 

You are right but I made a package mistake
they should go in fftw3-devel not in fftw3

> that's not insignificant. Here's what Volker is
> suggesting, I think 
> (with perhaps a few things moved around). I've put
> the "basic" 
> documentation in libfftw3-devel, and the "fancy,
> extra" documentation in 
> fftw3-doc).  You'll notice that with this division,
> the size is 
> distributed across the packages -- if not evenly,
> then at least 
> 'fairly'.  Also, in this scheme, the 'main' package
> (fftw3, the one 
> whose name matches the -src) contains only
> /usr/share README-style 
> stuff. That's a fairly common occurance for DLL
> utilitity libraries.
> 
> libfftw3_3:
> 520704   /usr/bin/cygfftw3-3.dll
>   70656   /usr/bin/cygfftw3_threads-3.dll
> ------------
> 591360 TOTAL
> 
> libfftw3-devel:
>    2202   /usr/bin/fftw-wisdom-to-conf
>   34816   /usr/bin/fftw-wisdom.exe
> 327332   /usr/lib/libfftw3.dll.a
>     762   /usr/lib/libfftw3.la
>   54536   /usr/lib/libfftw3_threads.dll.a
>     815   /usr/lib/libfftw3_threads.la*
>     209   /usr/lib/pkgconfig/fftw3.pc
>    2143   /usr/include/fftw3.f
>   10021   /usr/include/fftw3.h
>   51019   /usr/share/info/fftw3.info-1
>   51018   /usr/share/info/fftw3.info-2
>   44463   /usr/share/info/fftw3.info-3
>   43162   /usr/share/info/fftw3.info-4
>   11149   /usr/share/info/fftw3.info-5
>   1821    /usr/share/info/fftw3.info.gz
>   1743   
> /usr/share/man/man1/fftw-wisdom-to-conf.1.gz
>   2975    /usr/share/man/man1/fftw-wisdom.1.gz
> ------------
> 640186 TOTAL
> 
> fftw3-doc:
> 498555   /usr/share/doc/fftw3-3.0.1/fftw3.pdf
>   30406   /usr/share/doc/fftw3-3.0.1/fftw-faq.ascii
>           /usr/share/doc/fftw3-3.0.1/html/*
> ------------
> 919597 TOTAL
> 
> fftw3:
> 2121    /usr/share/doc/Cygwin/fftw3-3.0.1.README
> 173     /usr/share/doc/fftw3-3.0.1/AUTHORS
> 196103  /usr/share/doc/fftw3-3.0.1/ChangeLog
> 17992   /usr/share/doc/fftw3-3.0.1/COPYING
> 821     /usr/share/doc/fftw3-3.0.1/COPYRIGHT
> 9498    /usr/share/doc/fftw3-3.0.1/INSTALL
> 5346    /usr/share/doc/fftw3-3.0.1/NEWS
> 1253    /usr/share/doc/fftw3-3.0.1/README
> 1615    /usr/share/doc/fftw3-3.0.1/TODO
> ------------
> 234922 TOTAL
> 
> 
> However, putting the DLLs in a separate, standalone
> package is not just 
> about download size.  It also helps with package and
> dependency 
> management, if the API of the library changes in a 
> backwards-incompatible manner.

I am not really convinced, but I will split fftw3 
in at least 3 packages as requested and modify the 
various setup.hint accordingly.

fftw3
libfftw3_3
libfftw3_3-devel (or fftw3-devel)

I do not see reason to leave fftw3-doc as separate
package, the documentation should go in 
the devel package.

Regards
Marco



      ___________________________________ 
Scopri il Blog di Yahoo! Mail: trucchi, novità, consigli... e la tua opinione!
http://www.ymailblogit.com/blog/

Re: fftw3 and octave

[Dr. Volker Zell]

>>>>> Marco Atzeri writes:

    > I think (3) is more easy, as I already 
    > built and packaged them. 

    > http://www.matzeri.altervista.org/cygwin/qhull/
    > http://www.matzeri.altervista.org/cygwin/hdf5/
    > http://www.matzeri.altervista.org/cygwin/glpk/
    > http://www.matzeri.altervista.org/cygwin/suitesparse/

    > Can we leave them as a monolithic packages ?

I would split them now (splitting is fun with cygport). It's always more
trouble to get it right afterwards, as you can see with my latest ITA's
of Gerrit's monolithic packages.

Ciao
  Volker

Re: fftw3 and octave

[Charles Wilson]

Corinna Vinschen wrote:
> On Apr  1 00:02, Charles Wilson wrote:
>> So, we usually don't allow software in the distro that links against 
>> libaries that AREN'T part of the distro -- unless you take special care to 
>> distribute also those EXACT sources as part of your fftw3-src package.

s/fftw3/octave/

>> I'll leave this to Corinna and cgf to decide, but it seems to me that 
>> either:
>>
>> (1) you must rebuild your official package without reliance on Qhull, Hdf5, 
>> and qlpk/SuiteSparse, or
>> (2) include the EXACT Qhull/Hdf5/qlpk/SuiteSparse source code tarballs 
>> within the fftw3-src tarball

s/fftw3/octave/

>> (3) you [or someone else] must ITP these packages
> 
> 100% correct.

Well, except that when I said "fftw3-src" I should have said 
"octave-src". But it's mmot anyway, because Marco is pursuing option #3.

--
Chuck

Re: fftw3 and octave

[Charles Wilson]

Marco Atzeri wrote:

> fftw3
> libfftw3_3
> libfftw3_3-devel

Works for me.

> (or fftw3-devel)
> 
> I do not see reason to leave fftw3-doc as separate
> package, the documentation should go in 
> the devel package.

Sure.

--
Chuck

Re: fftw3 and octave

[Charles Wilson]

Charles Wilson wrote:
> Marco Atzeri wrote:
> 
>> fftw3
>> libfftw3_3
>> libfftw3_3-devel
> 
> Works for me.

Spoke too soon.  (Geez. I feel like a finicky old schoolmarm...)

  fftw3
  libfftw3_3
  libfftw3-devel

(that is, no '_3' DLL-number decorator for the -devel package)

The pattern for package 'foo' that provides the DLL cygmyfroboz-7.dll is 
usually

   foo-${VER}-${REL}.tar.bz2
   foo-${VER}-${REL}-src.tar.bz2
   libmyfroboz7-${VER}-${REL}.tar.bz2
   libmyfroboz-devel-${VER}-${REL}.tar.bz2
   (sometimes foo-devel, but not recommended).

However, when 'myfroboz' itself ends with a number (like bzip2: 
cygbz2-1.dll), then the pattern is the same except for the one that 
provides the DLL. So, if we had cygmyfroboz1-7.dll, then:

    libmyfroboz1_7-${VER}-${REL}.tar.bz2

So, in your case,
   foo == 'fftw3'
   DLL == cygfftw3-3.dll

So,

   fftw3-${VER}-${REL}.tar.bz2
   fftw3-${VER}-${REL}-src.tar.bz2
   libfftw3_3-${VER}-${REL}.tar.bz2
   libfftw3-devel-${VER}-${REL}.tar.bz2
   (e.g. no '_3' decorator on the -devel package)

Ex. bzip2:

   bzip2-1.0.5-2.tar.bz2
   bzip2-1.0.5-2-src.tar.bz2
   libbz2_1-1.0.5-2.tar.bz2     (cygbz2-1.dll)
   libbz2-devel-1.0.5-2.tar.bz2

--
Chuck

Re: fftw3 and octave

[Dr. Volker Zell]

>>>>> Charles Wilson writes:

    > So,

    >   fftw3-${VER}-${REL}.tar.bz2
    >   fftw3-${VER}-${REL}-src.tar.bz2
    >   libfftw3_3-${VER}-${REL}.tar.bz2
    >   libfftw3-devel-${VER}-${REL}.tar.bz2
    >   (e.g. no '_3' decorator on the -devel package)

    > Ex. bzip2:

    >   bzip2-1.0.5-2.tar.bz2
    >   bzip2-1.0.5-2-src.tar.bz2
    >   libbz2_1-1.0.5-2.tar.bz2     (cygbz2-1.dll)
    >   libbz2-devel-1.0.5-2.tar.bz2

Or in tabular form:

 o http://cygwin.com/ml/cygwin-apps/2008-03/msg00325.html

Ciao
  Volker

Re: fftw3 and octave

[Corinna Vinschen]

On Apr  1 18:51, Charles Wilson wrote:
> Corinna Vinschen wrote:
>> On Apr  1 00:02, Charles Wilson wrote:
>>> So, we usually don't allow software in the distro that links against 
>>> libaries that AREN'T part of the distro -- unless you take special care 
>>> to distribute also those EXACT sources as part of your fftw3-src package.
>
> s/fftw3/octave/
>
>>> I'll leave this to Corinna and cgf to decide, but it seems to me that 
>>> either:
>>>
>>> (1) you must rebuild your official package without reliance on Qhull, 
>>> Hdf5, and qlpk/SuiteSparse, or
>>> (2) include the EXACT Qhull/Hdf5/qlpk/SuiteSparse source code tarballs 
>>> within the fftw3-src tarball
>
> s/fftw3/octave/
>
>>> (3) you [or someone else] must ITP these packages
>> 100% correct.
>
> Well, except that when I said "fftw3-src" I should have said "octave-src". 

Well, ok, just 95% correct.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat