Date: Thu, 31 Jul 2003 02:45:46 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 164 ************************************************** Wednesday 30 July 2003 Number 164 ************************************************** Subjects for today 1 Re: UX2BS refresh : T.Sikora" 2 Re: UX2BS refresh : T.Sikora" **= Email 1 ==========================** Date: Thu, 31 Jul 2003 21:57:12 -0400 From: "T.Sikora" Subject: Re: UX2BS refresh Maynard wrote: > On Fri, 18 Jul 2003 18:20:23 +0200 (CEST), Stefan.Neis at t-online.de > wrote: > > >>>>With the current discussions about the future of EMX and >>> >>>it's successors > > > >>>Hi. Can somebody provide a current brief synopsis of >>>these discussions? > > >>Although I'm taking part in those discussion, I can't, >>really. I guess besides "there are different opinions which >>are just different", there's really nothing to be said. :-( > > >>From this and two subsequent responses (thank you), I reason and humbly > recommend that ux2bs take the opportunity to table further application > inclusion, and posix/2 devel, and solidify its current application base > for use with EMX; and bring its installation process to a > satisfactorily improved level (logging debugging feedback); and package > it up as a useful thing (go 'gold'), which generaly prepares for taking > the next step forward after the library issue becomes more clear. Sorry been out of the loop for a while working on some Zope projects with Jeff. I'll concentrate on making the bootstrap complete this weekend. I left off with wget almost completely working. I missed a couple routines. Rsync works fine. I'll be glad to include any 'newport_build.cmd' scripts anyone has or may build. My offer still stands for someone to take control of the ftp for changes/updates. I'll be glad to give you a user/pass to maintain it. I have it on rsync so all your changes will be migrated to all the mirrors nightly. Not much to do really except add changes that anyone may come up with. As for 'gold' with the bootstrap completed it really is already. It installs and builds perl everytime. The only issue is a cmd to bring up a window with the env set much like in Cygwin. The env and/or the config.sys is not changed so it's pretty much dead in the water after perl builds. This should be simple enough to do then we can effortlessly build those ports in the /build_system/scripts/build directory afterwards. It's so close. > > Announcing a delightful and useful tool such as ux2bs already is, could > bring more energy into the project. > > Thanks, > > -- Maynard > > > > > _______________________________________________ > UX2BS mailing list > UX2BS at os2ports.com > http://os2ports.com/mailman/listinfo/ux2bs > _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Thu, 31 Jul 2003 22:06:08 -0400 From: "T.Sikora" Subject: Re: UX2BS refresh T.Sikora wrote: > Maynard wrote: > >> On Fri, 18 Jul 2003 18:20:23 +0200 (CEST), Stefan.Neis at t-online.de >> wrote: >> >> >> >>> From this and two subsequent responses (thank you), I reason and humbly >> >> recommend that ux2bs take the opportunity to table further application >> inclusion, and posix/2 devel, and solidify its current application base >> for use with EMX; and bring its installation process to a >> satisfactorily improved level (logging debugging feedback); and package >> it up as a useful thing (go 'gold'), which generaly prepares for taking >> the next step forward after the library issue becomes more clear. > > Sorry been out of the loop for a while working on some Zope projects > with Jeff. I'll concentrate on making the bootstrap complete this > weekend. I left off with wget almost completely working. I missed a > couple routines. Rsync works fine. I'll be glad to include any > 'newport_build.cmd' scripts anyone has or may build. My offer still > stands for someone to take control of the ftp for changes/updates. I'll > be glad to give you a user/pass to maintain it. I have it on rsync so > all your changes will be migrated to all the mirrors nightly. Not much > to do really except add changes that anyone may come up with. As for > 'gold' with the bootstrap completed it really is already. It installs > and builds perl everytime. The only issue is a cmd to bring up a window > with the env set much like in Cygwin. The env and/or the config.sys is > not changed so it's pretty much dead in the water after perl builds. > This should be simple enough to do then we can effortlessly build those > ports in the /build_system/scripts/build directory afterwards. It's so > close. > >> >> Announcing a delightful and useful tool such as ux2bs already is, could >> bring more energy into the project. >> To further prove your point Maynard that ux2bs is useful I zipped up my build with some additions I added for Python and config.sys and Alex Newman set it up on one of his machines. He added GCC-3.2.1 and pretty much every port he's gone after builds. The UnixOS/2 distro is very formidable too. Uzipping the a/ap/d packages with a correctly written config.sys is almost identical in performance and even edges out the ux2bs in some respects. So in retrospect we all owe John a great deal. If a bonehead like me can do a few ports with it, it must really work. >> Thanks, >> >> -- Maynard >> >> >> >> >> _______________________________________________ >> UX2BS mailing list >> UX2BS at os2ports.com >> http://os2ports.com/mailman/listinfo/ux2bs >> > > > _______________________________________________ > UX2BS mailing list > UX2BS at os2ports.com > http://os2ports.com/mailman/listinfo/ux2bs > _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs