On 18 Jan 2011, at 11:09, Gianvito Pio wrote: > 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
I see, so my suggestion is to just remove the DLL from the package and declare it an external dependency, while to provide windows users with a ready-to-use package you should add your package to the precompiled packages in the windows installer, I think other packages do the same. would that be ok for you? 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
