Viktor:

Prior to continue, I must point that this is a 'friendly' message.

I respect you and your work. You (among others) made possible Harbour resurrection possible, when the project was almost 'dead'.

I don't agree with your
approach to distribute crippled Harbour.
Maybe we should have our license extended to not allow
that to happen.

IMHO, this is clearly contrary to Harbour project founders spirit.

They were very generous (Harbour exception in license demonstrates it). That decision towards against that spirit.

Since I'm using your Harbour distribution in HMG 3.0 test already published and considering that you do not agree with the way I'm using it, the right thing will be retire the involved files from SourceForge, until I create my own Harbour build from SVN (while license allows to me to do that :) ).

This way there is no point at all to give
general support on HMG site, as the toolset is a partial
one, not containing important parts. Even if these parts
are not to the direct benefit of all HMG users or developers.

Its your decision.

If your goal is to supply a compact package for users,
IMO you should simply just not include Harbour itself
and mingw, but rather simply install into existing Harbour
install and provide links to Harbour installer to users.

Because Harbour distribution is not compact :)

And it goes against other of the HMG principles: To be easy to use and install.

We haven't been talking about bug reports, we've been talking

Sorry, I was talking about that.

 > So if a user comes by and says, "I've installed HMG and I'd like
to create a hello world app, how can I do it?", Someone could say:
"type hbmk2 hello.prg". User won't know what I'm talking about.

Instead he will find a COMPILE.BAT, which no Harbour developer
knows anything about.

So, to make this possible, HMG (as it is currently) should dissaper to be transformed in a folder in Harbour contrib?

I will not do that.

Usually all bug analysis start with getting to know how the app
was built, and many time the build process is at fault, or it
can even create strange results very difficult to anticipate.

I have not your knowledge about Harbour, but I think that using exactly the same compiler and libraries is very unlikely that such thing happens .

Regards,

Roberto.


_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to