#14 closed defect (invalid)
SET PATH problem
| Reported by: | fbakan | Owned by: | Yuri Dario |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | yum | Version: | |
| Severity: | Keywords: | ||
| Cc: |
Description
bootstrapping yum adds x:\usr\bin etc. to the beginning of PATH.
This can cause problems. For example: When mptn\bin\setup.cmd contains
hostid 127.0.0.1
the wrong hostid get's called.
I think it's better to add PATH and LIBPATH entries at the end and not at the beginning.
Change History (3)
follow-up: 3 comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Ticket moved to ports svn, http://svn.netlabs.org/ports/ticket/8.
Closed unless other issues will come up.
comment:3 by , 14 years ago
Replying to ydario:
Why do you have hostid in setup.cmd? never seen one placed by os2 installer.
You are right, os2 installer does not set it. But the entry once was the
workaround/solution for being able to start HobLinkX11 and gimp.
( for details see also this thread (german) http://de.narkive.com/2005/1/15/598099-hoblinkx11-gimp.html )
Probably it makes more sense to modify coreutils hostid to accept IP as parameter.
Why do you have hostid in setup.cmd? never seen one placed by os2 installer.
Probably it makes more sense to modify coreutils hostid to accept IP as parameter.