installation --where to put things

I started to bring this up a while back.  Here it is again.

The plugins and ability to build them on demand requires some 
installation changes ,,

We have:
- the main program
- utility programs
- plugins that are loaded automatially
--- source
--- compiled
- plugins that are loaded on demand
--- source
--- compiled
- include files
- configuation files

Did I leave anything out?

Utility programs do need to be in a "usual" place, because they 
can be run separately.

Suppose we have prefix, and I like to keep it simple ..

/prefix/bin
/prefix/lib/auto/source
/prefix/lib/auto/compiled
/prefix/lib/demand/source
/prefix/lib/demand/compiled
/prefix/include
/prefix/config

To the old one, Dan commeted -- be sure to include the version 
number in the path.

I add to that -- and the architecture, like "netbsd" or 
whatever.

I am thinking that can be part of /prefix/, because different 
people have different ideas of how that should be set up.  
The "configure" script should default to a way that includes 
all that.

/prefix/ is likely to be something like:
 /usr/share/gnucap/1.0/x86_64-linux-gnu
Autoconf users will probably just say "/usr/share" for this.  
The rest will be automatic.

Putting it all in /prefix/ makes it easy to install and 
uninstall .. just "cp -r" or "rm -r".  Even if we use tools to 
do it, it is nice if it is clean under the hood.

Executables can be symlinked to /usr/local/bin or whatever.

The user's home can also have a ".gnucap" with a similar 
structure, and there can be another one for site files.

The "plugins that are loaded automatically" are specified for 
loading just by putting  them in the correct 
place, /prefix/lib/auto/source or /prefix/lib/auto/compiled , 
or a subdirectory.

The "plugins that are loaded on demand" are in the "demand" 
directories,or a subdirectory off there.  They would be loaded 
with the "attach" command or "-a" command line option.


Comments???