On 10/2/07, Mike Sullivan <Mike.Sullivan at sun.com> wrote: > S h i v wrote: > > > > I shouldn't need to tell this, but we use our own install-sfw ;) > > yep - but if you use such a script, ideally it's supposed to be > derived from what 'make install' would actually do. It shouldn't > put things that 'make install' would put in /usr/bin in /home/mike_s > for example, or ship the coolest expect script you've written :) > > the point is that things should be installed that one would expect, > and where folks would expect to find them (ignoring the current > /usr/sfw situation). though that can also be modified by discussions at > ARC (such as shared vs static libraries) and what other distributions > do (but that probably falls into determining what is 'expected'). >
Ok. For this case, the demo scripts being installed by make install into /usr/bin. Before moving them to demo, I had checked with debian and had found that it doesn't install any of these. IIRC, ActiveTcl one major tcl supplier on various platforms installs into a custom demo directory under /opt/ActiveTcl. Also I have experience in using tcl/expect and can say these are not mandatory. While checking for the license info, I noticed that there are lot more example files that the "make install" of expect doesn't install nor do we. -Shiv
