Re: ANNOUNCE: freeWrap 6.1 released

joey@swri.edu wrote:
> 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?

Yes. I knew about that restriction. I guess it never occured to me that
a program would want use a filesystem command on itself. Can you not
simply special-case the starkit itself? That is, put a wrapper around
glob so that if you're globbing something that should return the
startkit, you append [info nameofexecutable] to the result? Likewise for
auto_execok and the file commands.

I can understand though, how this would be problematic if you're writing
something like a file manager.
Received on Thu Sep 29 14:36:16 2005