[SEToolkit-developer] Fwd: Some questions regarding install locations

[Alex K. <ale...@gm...>]

On 13/06/07, Dagobert Michelsen <da...@ba...> wrote:
> Hi Alex,
>
> I managed to build a package for blastwave, however the structure
> is quite different:
> - the include files are in $prefix/share/se/include instead of
>   $prefix/include
> - the examples are in $prefix/share/se/examples instead of
>   $prefix/examples

So, I that matches the layout you get with a simple --prefix? I think
we had a conversation in the past where we talked about changing some
of that - I'm afraid I've been off on a number of other things, so
I've somewhat forgotten where we were...

> - the se-binary is now in $prefix/libexec/se.`isainfo -k`
> - $prefix/bin/se is now the script in $workdir/bin/se

If we put the binaries into sparcv7/sparcv9/i86/amd64 subdirectories,
we could use a simple isaexec wrapper (this is what I've used for our
internal stuff for several years), assuming we didn't want to deliver
sparc/x86 within the same package:

#include <stdlib.h>
#include <unistd.h>

int
main(int argc, char *argv[], char *envp[])
{
       return isaexec(getexecname(), argv, envp);
}

I was never very happy with all the voodoo which the se script did
with respect to picking up stuff magically.

> I think it would be a good idea to use these new pathes and
> provide links in the package from the old locations.
>

I agree on the new paths - seems like the right time to make setoolkit
more like everything else (and for blastwave so it fits properly into
the /opt/csw tree).

Is one approach to deliver a RICHPse package which is just a symlink
farm across into CSWsetoolkit (assuming that's what you're naming the
package - I'm just guessing here)?

--
Alex Kiernan