[Omake] SVN Commit: OMake Build System [0.9.8.x] (Rev. 10637)

Jason Hickey jyh at cs.caltech.edu
Fri May 4 11:15:32 PDT 2007


I hate to say it, but this suggests an alternative that, in the end,  
may be more productive.  The idea is to enforce sensitivity even in  
case-insensitive (but preserving) filesystems.

    - Make sure that Omake_cache.stat is strict, case-enforcing.
    - Remove all the case-code in Omake_node, and assume that
      filenames are always case-sensitive.
    - Move the case-sensitive detection code to Omake_cache,
      for use by Omake_cache.stat.
    - Document the fact that we choose to be case-sensitive.

If the goal is portability, this is actually the right way to go.  If  
desired, we might translate the targets on the command-line.

For osh, the current node-detection model might be better.  But  
again, if we care about portability of osh scripts, it is better to  
be strict.  We can add a function that mimics realname(3), so  
programmers can be explicitly sloppy.  Besides, the normal system  
calls will work as usual, it is just Omake_cache.stat that is changed.

Jason

On May 4, 2007, at 10:48 AM, Jason J. Hickey wrote:

> Here is a proposal for fixing the case-sensitive problem.

--
Jason Hickey                  http://www.cs.caltech.edu/~jyh
Caltech Computer Science      Tel: 626-395-6568 FAX: 626-792-4257





More information about the OMake-Devel mailing list