<Big Snip>
The csh & tsch ports we currently have require alot of work to make them, well, work, so those are a dead end, when the time comes we'll need to revisit this issue, but for now it's best we focus on tasks we can use on the short term.
Sorry for missing the meeting on Monday, I broke down in the fast lane on the M1. A rather harrowing experience I can tell you. Onto the message
Whilst I hate to contradict our benevolent dictator, this could be a mistake why?
well, whilst its very good to get the other utilities(dependancies) ported and it will provide some output for the project (always a good thing), if we dont start thinking about csh/tcsh now, and getting something at least started we will come to a point (fairly rapidly from what i can tell - at least as far as projects go) where we will come to a complete stop because of their lack of availability. What we should be doing is using a schedules to plan when we will be doing something about the issue, now we obviously cant plan based on time, as all the programmers are doing this in their spare time, we can do it based on acheivements (provided the project plan is set up correctly), so ie when 50% of dependancies are complete we need to start on build environment etc. This is one of the reasons it makes sense to have a top level porject (say dependencies) and then sub projects for all of the apps that need porting, you can then see at a glance the percentage complete of the dependencies top level project.
This also applies to the bash shell (abc-shell??) which will be needed to help port the dependancies I believe (along with automake/conf etc)
Mark