Thanks for your reply Carlo.
Yes,  the DLL is copied to octave/bin folder only when the package is
installed on windows and it's a windows implementation of POSIX thread
library.
We thought to include it (that is for windows users only) to provide a
ready-to-use package, also because it works on both 32 and 64bit windows.

Option 1) Just declaring it as external dependency isn't so good, because in
that case the package installation would be trickier for windows users. But
in this way the categories 1,2 and 3 won't download anything more than they
need.

Option 2) About the alternative of including the source code...you asked me
why the users of categories 1,2 and 3 should download that 100kb DLL.... but
if we include the source code and the makefile the question could become
"why the users of categories 1,2, 3 should download about 180 files of
sources (about 1MB)" ?

So, if we really have to remove the DLL I think it's better the option 1
...

Any other suggestion? Thanks

2011/1/17 c. <[email protected]>

>
> Gianvito,
>
> First of all thanks for your contribution and welcome to the OF community!
>
> On 17 Jan 2011, at 20:11, Gianvito Pio wrote:
>
> > Thank you,
> > we will fix the points 1 and 3 immediately...
> > But what about the point 2? Should we put the source code and the build
> > instructions in the src directory?
> >
> > Thanks
>
>
> Actually even better would be to remove pre-built binary libraries
> completely and either
>
> - specify them as external dependencies that
>  the user needs install prior to installing the package.
>
> - include source code and a makefile to build the library
>  when the package is installed.
>
> To my knowledge, no other package includes pre-built binaries and I believe
> this policy makes a
> lot of sens from the point of view of portability.
>
> If I understand correctly the .dll file you included is meant to provide a
> POSIX compatible
> pthreads library when installing the package on windows, so this lbrary is
> not needed :
>
> 1 - for all users who are fortunate enough to not run windows
> 2 - for windows users who install octave via cygwin
> 3 - for users of the migw32 who only install packages that are included in
> the binary
>    octave installer and never do "pkg install" themselves
>
> so why should users of categories 1,2,3 also download your .dll file?
>
> c.
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to