пятница, 2 августа 2013 г., 3:13:23 UTC+4 пользователь Gregory Szorc написал:
> Are there any objections to this proposal? Hello everybody, I'm the person who's being actively working now on getting Mozilla build on OS/2 again with all the new IPC stuff in. As Peter said, at the present time we have no plans to push our patches but that's only because from my experience this process is very complex and we have very limited resources for working on that task (no surprise). So our idea is to get it all working again first, then create a smaller number of bigger (and logically consistent) patches and try to push them upstream — while still continuing development in our own repo so that we don't depend on how fast the patches are accepted etc. If anybody has a better idea, we are ready to consider it. What about switching the build system, it's not our primary task of course but it will be done sooner or later — this is all to have a more robust build environment and thus save some resources here too. An ideal solution for us in the future would be to put the build files of the new build system (Makefile.kmk, generally one per each subdir) upstream but I'm not sure if it will ever be accepted — this is another reason why we decided to stick to our own repo for the time being. In either case, removing OS/2 support from the existing makefiles - may be done (but better after we completely move away to kBuild). Regarding the main subject. There are many OS/2 parts that are still valid (e.g. the NSPR code) so if you will drop them we will have to reapply them back in our repo. And if we push it back later you will have to reapply them again. This doesn't make sense to me — if you are going to accept our patches at some later stage. If you are certainly not, then you may go on with that. I'm also ready to listen to any other ideas on how we can collaborate in this case. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
