Philip Blundell writes:
> >The 2.3 CVS tree.
> 
> That certainly did contain 7500 support last time I looked, assuming you are 
> talking about the one at netwinder.org.

Naturally.

> It's several years since I used Acorn C but I thought it did come with a diff 
> program.  Or one could use a Unix system for maintaining the source.  
> Regardless, this seems like a tangential issue to the question of whether to 
> actually release source or not.  LinLoader is GPL'd so there is an existence 
> proof that RISC OS free software is possible.

It's certainly not tangential at all.  It's a question of the amount of time
and tools.  There is a diff program, but it does not produce any sort of
output that could be passed into a patch-type program.  The output of !Diff
is only useful for documentation purposes.

This lack of a standard diff/patch is /the problem/ and /the reason/ why it's
not open-sourced.  If someone can show me a practical solution to this, then
it will get open-sourced.  Until that time, it remains as is.

Also, it's worth noting that !Linux cannot be linked by the newer Acorn tools,
since the AOF format has changed in non-backward compatable ways (which prevent
the non-source distributable library which the programs link against linking).

Basically, development on RISC OS is a mess, just like partitioning stuff on
Acorn machines.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       [EMAIL PROTECTED]      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++        Please use [EMAIL PROTECTED] for           ++
++                        kernel-related discussions.                      ++

Reply via email to