> > > - gcc specific hbmk script: hbmk2 is meant to replace it. > > - rename hbmk2 to hbmk. > > I'd like to hear opinions. > > I agree that hbmk2 is a step in the right direction, but I don't think > we should remove hb* scripts in 1.1 ( I use only *nix envs + > msys/mingw I can't say much for Win based ones ). > > IMHO doing "big" changes between two consecutive releases creates a > sense of "instability" and makes harder to test the svn since a user > needs save the old env, do the changes, do the tests and restore the > env.
I mean that ideally a 1.0.1 user should be able to install 1.1 and > build his apps without any single change. Release 1.2 can drop what > 1.1 has been previously declared deprecated and so on. We also need to care about 3rd party projects. They may need the time > to make the required changes. We're here talking about the make and build systems. Which doesn't have much to do with 3rd parties, after all everyone can download the binary release pre-built and don't care about it. As for hbmk, it's just one tool, and hbmk2 is even compatible. We can keep the hb* scripts for *nix (except hb-mkslib which is IMO nit-picking and doesn't really interferes with large amounts of users, even then it's easy to solve with one command locally). Also the GNU-make system works in 1.0.1 also so it can be used with both releases for the most part. For the programmatic POV we do exactly like you suggest, and IMO this is much more important. Overall I see no point to limit ourselves to the state of year ~2000 with regards to the build/make system and exact file compatibility down to the exact names and envvar usage. Let's look forward, that's what I'd say, otherwise we never reach anywhere. What I'd suggest is to gather all changes into one document, or even better, _finally_ clearly document the make methods and make them simpler, so everyone can easily adapt in one pass to the 1.1.x way. I've started this with /INSTALL, plus most thing are already in whatsnew.txt Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
