Re: ANNOUNCE: freeWrap 6.1 released

Bryan Oakley <oakley@bardo.clearlight.com> wrote:
> joey@swri.edu wrote:
>
> > Here, hear! I think the same thing. Currently, I am using Starpacks,
> > but only because I need to support the Mac. Starpacks are really complex
> > and for us have actually caused some problems because of the wrapping
> > mechanism and the fact that certain commands no longer work under a
> > starpack with no workarounds.
>
> Out of curiosity (I don't use starkits much, as I keep landing at jobs
> that use other techniques) what commands no longer work that are causing
> you problems?

The ones I have found are auto_execok, file, and glob. The problem is
the name of the executable is now a directory so commands which would
normally work for the starpack as a file now no longer work from within the
starpack on the starpack itself. Does that make sense?

For example, if you have a starpack named "PROG": "file mtime PROG" from
within the starpack PROG returns 0. "auto_execok PROG" returns false from
within PROG even though PROG is a perfectly fine executable in the path.

The reason is so you can use the file, glob, and auto_execok (maybe?)
on files within the starpack itself. This is great if that's what you need
to do; however, it will not work as before if you were expecting to use any
of these commands on your new starpack. As far as I know, there are no
workarounds either. :-(

Joey
Received on Thu Sep 29 14:36:16 2005