On Sun, Aug 10, 2008 at 05:54:52PM +0400, Andry wrote: >>On Sun, Aug 10, 2008 at 01:31:54AM +0400, Andry wrote: So, in other >>words, you redescribing the problem that has already been identified. >>You just wanted to spend a paragraph getting your kick in. >I describing a set of problems. > >>And, unless the packages are doing something odd like moving their info >>files around in postinstall scripts, it shouldn't matter when >>_update_info_dir is run. > >It already should, because it at least should run after "bash" or "ash" >component.
This only matters if there is no /bin/sh set up by postinstall, which is the bug that was uncovered by this thread and is a bug which is being addressed. >>You mentioned _update_info_dir. If _update_info_dir is installed then >>install-info.exe is also installed. install-info *does* need to be >>installed to correctly set up the directory file for use by info. >I mentioned install-info, i didn't said anything about _update_info_dir >does install intall-info. Installing _update_info_dir will cause install-info.exe to also be installed since it is a dependency and post install scripts are run after all packages are extracted. >I told about postinstall scripts at all, they uses install-info without >checking it on presence The postinstal scripts can rely on its existence if they have .info files. That is precisely why _update_info_dir was invented. >half scripts just run it like "intall-info" instead of >"/usr/bin/install-info", because PATH IMHO can be unupdated yet for >searchpaths. So i additionally fix postinstall scripts to fit my >needs. I'm sure all of the scripts assume the existence of a sane path. I believe that bash defaults to a useful path if there is none set. But if setup.exe isn't setting up a basic PATH it probably should do that. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
