Hi Marek,
I did not investigate zlib/hbzlib problem. After all,
currently it's in contrib. But my experience with some
I know, but we plan to add it in full source into /src/
- gt*, rdd* separate or not? (IMO separate)
I disagree. Having them as separate libraries has no advantages.
I just made some tests with GTs under BCC and including them in
link command changes *nothing*, until you *explicitly* REQUEST
a particular GT. So having them as separate libraries give us
nothing except complications in further link command, as oposed
to putting a *simple* REQUEST in prg source with one common lib.
I know it makes no _technical_ difference.
I like it better still, because these are "plugins" in a sense.
- Purpose of hbnulsys?
AFAIK it allows to build programs which do not require *any*
DBF access. It's serves as a plumbing. It has to be a separate
library. Thanks for pointing this.
Question is, what benefit does it have over including a random
RDDs? (executable file size?) Especially if we end up including
all RDDs to one unified harbour lib.
Finally, VERY important, but not strictly related to that:
Solving the obligatory inclusion of every LICENSE files
in every distribution (binary/source) we release.
I think we have to include ALL such licences either in source
or binary distributions.
I've checked the win32 beta3 binary distro, and it indeed have
COPYING in the root (dunno about others). We seem to miss the
license of PCRE/ZLib-MiniZip though.
We should investigate whether we must include any 3rd party
license texts. If the answer is yes, we must include these
as well (like LICENSE_PCRE.txt, LICENSE_ZLIB.txt) in both
binary and source distributions.
IMO we have to.
I agree.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
