Re: Binary compatibility issues with Hugs FFI

[Antti-Juhani Kaijanaho]

On Thu, Aug 26, 1999 at 08:29:46AM -0600, Alastair Reid wrote:
> Also (ie if you don't buy this interpretation), I think the FHS
> requires that all files in /usr/share/blah to be architecture
> independent but I don't think it requires all architecture independent
> code to go in /usr/share/blah.

Well, /usr/lib is restricted to arch-dependent stuff only, and I don't
know what other place would be appropriate.

Ok, here's a concrete draft proposal:

  Install all Haskell source files for a particular application somewhere
  else than in the directories specified here.  The main module may be
  installed in /usr/bin (/usr/local/bin for local installs) if it is a
  proper runhugs script.  The same goes for FFI shared binary objects
  private to a particular application.
  
  Public Hugs 98 extension modules that include *only* Haskell
  source should be installed in /usr/share/hugs98/extensios
  (/usr/local/share... for local installs).
  
  Public Hugs 98 extension modules that include FFI shared binary objects
  should be installed in /usr/lib/hugs98/extensions (/usr/local/lib... for
  local installs).  It is permissible to install the Haskell source
  files in /usr/share/hugs98/extensions and symlink there the shared
  binary objects from /usr/lib/hugs98/extensions.

  Hugs 98 installations that follow this convention will by default
  use the default search path
    
-P/usr/local/lib/hugs98/extensions:/usr/local/share/hugs98/extensions:/usr/lib/hugs98/extensions:/usr/share/hugs98/extensions:{Hugs}/lib:{Hugs}/lib/hugs:{Hugs}/lib/exts

How does this sound?

-- 
%%% Antti-Juhani Kaijanaho % [EMAIL PROTECTED] % http://www.iki.fi/gaia/ %%%

   "... memory leaks are quite acceptable in many applications ..."
    (Bjarne Stroustrup, The Design and Evolution of C++, page 220)