Re: intent to package TETware and VSX-PCTS from TOG
On Tue, 12 Jan 1999, Jules Bean wrote:
> On Mon, 11 Jan 1999, Dale Scheetz wrote:
>
> > Without suggesting /opt/TET as the home for this package (something that
> > even I don't really like) I am left with a selection from /usr. While I
> > can see arguments for /usr/lib, /usr/share, and even /usr/src, I have no
> > idea which is correct for this application. I am sure that there are some
> > of you with a better opinion than myself. I hope you will share it ;-)
>
> A common solution is to put everything in /usr/lib/TET, (assuming it's
> basically architecture dependent, that is) and then put in /usr/bin either
> symlinks or wrappers for common tasks/all possible tasks (as appropriate
> for the application concerned).
I too am leaning toward /usr/lib/TET3 as the preferred directory. However,
the package doesn't satisfy any of your criterion. It is not architecture
independent. $TET_ROOT/bin contains tcc (the "test case coordinator")
which is an executable binary. On the other hand, the package could
configure and build the binaries at install time, thus making it arch
independent, but requiring that the source and build scripts be included
in the package. If I prebuild the binaries, I can put the source and
header files in a tet3-dev package for use developing additional test
suites, that need not be installed if testing using existing test suites
is the goal.
As I told Marcus, there is little to be gained by installing binaries and
libraries in "standard" locations, as they are never used that way by the
testing software, guaranteeing the integrety of the testing environment.
Thanks,
Dwarf
--
_-_-_-_-_- Author of "The Debian Linux User's Guide" _-_-_-_-_-_-
aka Dale Scheetz Phone: 1 (850) 656-9769
Flexible Software 11000 McCrackin Road
e-mail: dwarf@polaris.net Tallahassee, FL 32308
_-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_-
Reply to: