On 01/17/2013 03:00 PM, Patrick O'Callaghan wrote:
On Thu, 2013-01-17 at 22:07 +0800, Ed Greshko wrote:
I noticed that during the erase action, yum showed the repo as
"@google-chrome/17", but during the install it shows as
"google-chrome".
The Chrome versions are exactly the same, so as you say there is
clearly
some magic happening during the install which is different from F17
to
F18.
FWIW: The magic is in google-chrome-stable's %postinstall scriptlet:
# rpm -q --scripts google-chrome-stable
....
# Fedora 18 now has libudev.so.1. http://crbug.com/145160
LIBUDEV_0=libudev.so.0
LIBUDEV_1=libudev.so.1
add_udev_symlinks() {
get_lib_dir
if [ -f "/$LIBDIR/$LIBUDEV_0" -o -f "/usr/$LIBDIR/$LIBUDEV_0" ]; then
return 0
fi
if [ -f "/$LIBDIR/$LIBUDEV_1" ]; then
ln -snf "/$LIBDIR/$LIBUDEV_1" "/opt/google/chrome/$LIBUDEV_0"
elif [ -f "/usr/$LIBDIR/$LIBUDEV_1" ];
then
ln -snf "/usr/$LIBDIR/$LIBUDEV_1" "/opt/google/chrome/$LIBUDEV_0"
else
echo "$LIBUDEV_1" not found in "$LIBDIR" or "/usr/$LIBDIR".
exit 1
fi
}
...
It's a really dirty hack, but they seem to believe it's sufficient.
Also, they have a similar hack for libbz2.so.* in there.
Ralf
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
