On Tue, Nov 18, 2008 at 3:18 PM, Przemyslaw Czerpak <[EMAIL PROTECTED]> wrote:
> I do not agree. You both are thinking only about your current needs. > I want to be able to write Harbour applications as scripts or > binaries and distribute them in system friendly packages like > RPM or DEB. It means that I need Harbour installed in known > ... > which will keep some basic rules between platforms or we > will have serious problems with portability. I think we have 3 different situations: 1 - Linux well known and accepted standards like RPM and DEB and most of the dependences are available within the "official" repository ( f.e. zip, openssl, gd, postgresql, mysqll and so on ) 2 - Win here we have a standard way of install ( setup.exe ) but things get complicated since we support many different C compilers and there is no a simple way to get dependences 3 - OSX the tool that create packages comes with the OS but it's not easy to get dependences and there very few ( 2 ) users, also there are 2 arch ppc and Intel Now Linux situation is in the best shape since RPM and DEBs are supported ( but we also have the cross-platform options Linux-W32 Linux-WinCE ) Win it's completely different if a developer want to use msys/mingw ( like me ) or other "native" compilers like MSVC xyx, BCC xyz, .... It's different where to get dependences and how to build programs ( hb* scripts vs batch files ) In OSX is even more complicated by the fact that we've only 2 developers and at least for me with a very basic knowledge of the dev tools. Now it seems we're missing the main point: Why should a non-Clipper developer choose Harbour instead of PHP, Python, Java, .Net or whatever else? and how can Harbour attract other Linux, OSX, Win developers? Can we imagine an OSX developer that choose Harbour without a GUI? Can we imagine a web developer that choose Harbour without an Apache module? Can we imagine an SQL developer that choose Harbour without an Oracle module? I think we ( mostly you ) should define the goals and check where to find the resources to achieve them. If we're a small group of old Clipper developers that need to maintain its legacy apps than the goal was achieved with 1.0 if not it's time to make choices. However I'll start to look at the OSX packager and I'll report best regards, Lorenzo _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
