Project Looking Glass

Hi Daniel,

Apart from our updated Xserver most of our binaries are actually jar
files so I don't think they belong in /usr/lib itself, let me give some
more detail....

Currently for development we have everything under one directory, the
structure looks like this

lg3d
    ext                           Supporting jars for both core and
bundled apps
    ext-unbundled         Space for app specific supporting jars
    lib                           The main platform jars and native
.so's for X server binding
    resources                  Images etc
    bin                           Shell scripts to start everything
    etc/lg3d                    Config files

For deployment the etc/lg3d directory obviously becomes /etc/lg3d and
the scripts in bin probably belong in /usr/local/bin. For everything
else there seem to be a number of choices, the best of which I think are

1)  The .so's go in /usr/lib/lg3d and everything else goes in
/usr/share/lg3d. Apache-ant seems to follow this approach.

2) The .so's and all the jars go in /usr/lib/lg3d (various sub
directories) and the resources  go in /usr/share/lg3d

3) As we are providing a window system platform we follow the precendent
set by X and put everything (except etc) in /usr/lg3d as a sibling of
/usr/X11R6

OpenOffice and gcj seems to have jars in both /usr/share and /usr/lib

My preference would be either 1 or 3 as it keeps the bulk of the
components together. What do you think ?

Cheers

Paul

Daniel Stone wrote:

>On Thu, Nov 17, 2005 at 04:18:09PM -0800, Paul Byrne wrote:
>  
>
>>I'm proposing to install our binaries in /usr/share/lg3d and our
>>configuration files in /etc/lg3d, not very contraversial I hope ;-)
>>    
>>
>
>Uhm ... binaries go in /usr/lib, rather than /usr/share; that is, if
>they're internal-only.  Binaries that users run should go in /usr/bin.
>
>  
>
>>A trickier question, we provide a slightly modified Xorg server (all the
>>source is in the Xorg cvs). It run's GNOME etc without any problems but
>>provides some new features we need. What is the correct way to have the
>>system start our X server rather that the default one, use the
>>update-alternatives mechanism ?
>>    
>>
>
>Look into the xserver-xorg package's maintainer scripts, in its
>interactions with default-x-server; you'll need to do much the same.
>
>Cheers,
>Daniel
>  
>