setup readme possibility (was about nano)

Christopher Faylor cgf@redhat.com
Thu Oct 17 18:29:00 GMT 2002


On Fri, Oct 18, 2002 at 11:22:34AM +1000, Robert Collins wrote:
>On Fri, 2002-10-18 at 11:19, Christopher Faylor wrote:
>> On Thu, Oct 17, 2002 at 09:16:55PM -0400, Christopher Faylor wrote:
>> >Actually, the shell script could also look for the standard .bat and .sh files.
>> >Executing them in one window would stop all of the black boxes from flashing
>> >after setup completes.
>> 
>> This all relies on the existence of /bin/sh of course.  Probably /bin/sh should
>> be built into setup.exe.  Yeah, that's the ticket.
>
>
>I reckon there's no need for this cygwin1.dll that keeps giving everyone
>problems. All we need to do is put it into setup.exe, and we'll all be
>happy :}.

Now we're on a roll!

>Seriously though, I want to keep the logic for *what* package scripts to
>run in setup.exe for now. The prime reason being that as we get more
>advanced in install order and dependencies, we may want to set specific
>script orders, rather than just alphabetic.

I could imagine a scenario where setup.exe could still organize things on
disk or generate one shell script to run everything.  You just have to
put that in the appropriate place for the "final" script to execute it.

Regardless, what about the idea of having a script that is always run
when everything else is done, though?  It would just be for things that
always needed to be fixed up.  For instance, I'd welcome the ability to
be able to run mount to reset the /bin directory to 'cygexec' mode after
setup is done.  I have to remember to do it every time I run setup now.
If I could just add a user post-install script that would be helpful.
I can also imagine a scenario where the /usr/info directory is always
scanned to make sure that 'dir' is up-to-date.  Hmm.  I wonder what made
me think of that?

cgf



More information about the Cygwin-apps mailing list