[Bug 202521] Review Request: RutilT

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: RutilT


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202521


kwizart at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|                            |NOTABUG




------- Additional Comments From kwizart at gmail.com  2006-08-15 08:07 EST -------
Hello!
The script make install exist but cannot work well with %RPM_BUILD_ROOT (ie: the
binary searches icons in /var/tmp/RutilTv0.11-buildroot/usr/share/rutilt where
it should be /usr/share/rutilt. I was using sh configure.sh
--prefix=$RPM_BUILD_ROOT%{_prefix}  - So i've just noted where make install
place files and use normal prefix to manual install files...


What is the regular way of updatating the .spec file?
- Make a patch and import (what's the old/new name?)
- Upload to new version of the .spec on my website?

Quote of INSTALL file:
"  - Rutilt helper's install path has changed between v0.07 and v0.08. Before,
it was /usr/libexec/, it's now /usr/local/share/rutilt/. Ditto with the main
binary, is was previously installed in /usr/bin/, it's now in /usr/local/bin/.
Make sure you erase the old binaries.
...
    - "make install" installed the program in /usr/sbin before v0.06, it's
now /usr/bin. Make sure you erase your old binary."

-> so maybe i can change from /usr/share to /usr/local/share? what is the name
of this directory for using in a spec file? But INSTALL is not really clear so
i've used path result of the make install script...

changed livna to extra and %{_datadir} png....
ExclusiveArch:	may be dropped (ppc version of the kmod-rt2500 may be very buggy )

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.