First run of esy-bash has extraneous output about esy-bash HOT 4 CLOSED

The output that breaks us is stuff like:

Copying skeleton files.
These files are for the users to personalise their cygwin experience.
They will never be overwritten nor automatically updated.
'./.bashrc' -> '/home/appveyor//.bashrc'
'./.bash_profile' -> '/home/appveyor//.bash_profile'
'./.inputrc' -> '/home/appveyor//.inputrc'
'./.profile' -> '/home/appveyor//.profile'

from esy-bash.

Unfortunately, I couldn't repro this locally on my machine. Still looking into it.

from esy-bash.

Thanks for testing it out @prometheansacrifice !

I think the issue is that, if you don't have a .bashrc/.bash_profile etc already, the first run of bash will create - this breaks the output we expect! So it might not repro locally if you already have those in your home directory.

I think there are a couple things we need to do here:

• Explicitly set the home directory - we can set this in the /etc/nsswitch.conf. We can set the home directory by using db_home. We could set it like: db_home: /usr/esy. We could include this modified /etc/nsswitch.conf in our bundle.
• Seed the home directory with the requisite scripts - we could just run bash.exe prior to packing to get the .bashrc/.bash_profile/etc generated

Explicitly setting the db_home here will help get the esy/cygwin isolated from another environment the user may have.

This solution would also address #15

from esy-bash.

Fixed by #35 - thank you @prometheansacrifice ! 💯

from esy-bash.