[Bug 1468] New: Rebuild of .src.rpm on clean system can't run regedit

http://bugs.winehq.com/show_bug.cgi?id=1468

Summary: Rebuild of .src.rpm on clean system can't run regedit
           Product: Wine
           Version: 20030508
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-misc
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

I am trying to build the latest .src.rpm on a clean RHL9 setup.  I've gotten to
the point where it wants to run the wineserver just long enough to run regedit
to populate a new registry with winedefault.reg.

Since there's no LD_LIBRARY_PATH pointing at the build-root's dlls/ or libs/
areas, wineserver cannot load.

If I work manually in the build-root with a good LD_LIBRARY_PATH, it does get
slightly farther.  But the miscemu/wine executable still has a hardwired future
path for ntdll.dll.so instead of relying on the LD_LIBRARY_PATH.

--------------------------------------------
...
+ sed 's|"Path" = "/c"$|"Path" =
"/home/halley/rpm/tmp/wine-20030508-root/usr/share/wine-c"|'
documentation/samples/config.rh
+ sed 's|"Path" = "${HOME}"$|"Path" = "/home/halley/rpm/BUILD/wine-20030508"|' -
+ WINEPREFIX=/home/halley/rpm/BUILD/wine-20030508/documentation/samples
+ programs/regedit/regedit winedefault.reg
programs/regedit/regedit: line 89: /home/halley/rpm/BUILD/wine-20030508
/home/halley/rpm/BUILD/wine-20030508/miscemu/wine: No such file or directory
programs/regedit/regedit: line 89: exec: /home/halley/rpm/BUILD/wine-20030508
/home/halley/rpm/BUILD/wine-20030508/miscemu/wine: cannot execute: No such file
or directory
error: Bad exit status from /home/halley/rpm/tmp/rpm-tmp.84491 (%install)

RPM build errors:
    Bad exit status from /home/halley/rpm/tmp/rpm-tmp.84491 (%install)
--------------------------------------------

This is true whether I'm walking through the .spec or the tools/wineinstall at
this point.

Possible recommendation I've not yet tried:  move the registry-populating work
out of the %install stage script, and into the %post stage script.  %install is
run on the *builder's* system setting up the built files which must be copied
onto a user's system and shouldn't rely on running the app just built (since you
are usually building as non-root, and without the app fully installed, etc). 
%post is for running on the *user's* system, and can use the full capabilities
and configuration of the user's permissions and system layout.

I really prefer the .src.rpm format to the tarball format.  It allows me to
incorporate, develop and offer patches easier, and it helps me track the package
for uninstalls later.  I've tried the past couple .src.rpms, and it's just not
able to get past this point.