More: [1.7] packaging problem? Both /usr/bin/ and /usr/lib/ are non-empty

Corinna Vinschen
Tue May 12 17:45:00 GMT 2009

On May 12 19:29, Corinna Vinschen wrote:
> On May 12 12:58, Charles Wilson wrote:
> > 2009/05/11 14:56:28 running: C:\cygwin-1.7\bin\bash.exe -c
> > /etc/postinstall/
> ...isn't that wrong?  bash is called from setup with a *script* as
> parameter, not with a *command*.  Shouldn't that be `bash',
> rather than `bash -c'?  
> > /cygdrive/h/.bashrc
> > /etc/postinstall/ line 9: cd: /usr/lib: No such file or
> > directory
> >[...]
> > That's just my ~/.dotfiles being chatty.  However, I wonder if
> > postinstall scripts should read ~/.dotfiles at all.  When bash is used
> > as sh, it doesn't read ~/.stuff.  However, notwithstanding
> And I'm really wondering if your .dotfiles script isn't the problem
> here.  Why is it read anyway?  Do you have a $HOME in your Windows
> environment?  After all, $HOMEDRIVE$HOMEDIR isn't utilized anymore
> to generate a $HOME in Cygwin.
> > above, many of my package's postinstall scripts make use of bashisms, so
> > I put /bin/bash in the #! line.  It's probably not a good idea for setup
> > itself to invoke the post/pre scripts using interpreter-specific flags
> > like -norc because some postinstall scripts might be in other
> > languages...Do we have a policy about this?  Should I use '#! /bin/bash
> > -norc' instead?
> Shouldn't setup better use the --norc option?

Why does bash read an rc file at all?  The man page claims that only
interactive bash shells read profiles and non-interactive bashes only
read an rc script if $BASH_ENV is set.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-developers mailing list