I am grateful for your efforts and I am not trying to denigrate them. However, "contradict" is a strong word and I do not think the situation is nearly as clearcut as you think, your last comments above appear to support my point. I, personally, would like to see most of contrib, including qt, moved to a separate project. I am also content to be a minority of 1 and will cease to make waves about it.

Moving contribs in and out is a permanent subject since long and
aside from the politics and other non-technical issues, I plan to
make some steps in the future to make it possible to very easily
make such move, without causing any sort of technical difficulties.

IOW, it will allow us to move any contribs out of our repository
easily. Also, if 3rd party libs adopt these methods, it will also
be very easy to move any of them in our contrib sections.

It all comes down to the make system. contribs use our GNU Make
system, but this isn't an option when moved outside, or for any
3rd parties. So what can be done here is to change our contribs
to use hbmk2 instead of GNU Make. Of course there are issue to
solve, and such move won't happen in short term.

Anyhow it would be nice, since contrib/3rd party lib development
could be moved to a common make system, simplifying the current
overall chaos in this matter.

[ PS: I've been in favor of moving contribs to a separate project
many years ago, but since "quality control" is much better / simpler
when these contribs are in our repo (and their quality start to
reach the core one), I no longer agree with such move in general.
There may be specific contrib exceptions of course, and there
may be other factors in this equation. ]

Brgds,
Viktor

_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to