Yes, Greatlord brought this to my attention today as well. I wasnt
planning on moving ROS cmd into Wine really. I was more planning on
moving Wcmd into ROS(Yes, I would have to talk with other ROS devs about
this idea first I'm aware) and then filling in all the features that
arent competele. Greatlord said that there might be problems doing that
as well with the way wcmd is coded. To be honest, I havent spent much
time looking into the specifics of the project yet, it is more of
something that has been in the back of my head which I wanted to do
during my summer break.
Brandon
Steven Edwards wrote:
Hi Brandon,
On 4/21/06, Brandon Turner <[EMAIL PROTECTED]> wrote:
Not to take anything away from someone that wants to do a SoC project.
But I'm a ROS dev and I know you guys arent taking patches from us right
now but that aside, one of my shorter term goals is to try and sync
wcmd(if it is what i think it is, i dont use linux / wine often so maybe
im misintercepting it) with the ROS cmd. So just keep that in mind. I
would also be more then willing to mentor someone for this project,
assuming I am not disqualified based solely on the fact I am a ROS dev.
The real issue is the ReactOS cmd and wcmd do not come from the same
code. ReactOS cmd as you know is a 32bit port of the freedos cmd where
wcmd is a totally new implementation. The reason for this is because
its LGPL where FreeDOS and ROS CMD are GPL. Alexandre has stated in
the past that he does not object to having GPL tools in the tree if
there is no other option however most users don't need 100% cmd.exe
compatiblity so getting Wine to adopt ReactOS cmd (all other issue
aside) is going to be next to impossible.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
