Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 232278 - wrong plugins location
Summary: wrong plugins location
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: lat
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-03-14 17:41 UTC by Fabrice Bellet
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 1.2.2-2.fc6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-19 15:35:43 UTC


Attachments (Terms of Use)

Description Fabrice Bellet 2007-03-14 17:41:42 UTC
Hi,

lat-1.2.2-1.fc6 expects to find its plugins viewers in /usr/lib/lat/plugins or
in ~/.lat/plugins, but does not look in /usr/lib/lat. The consequence is that
the "Views" window doesn't show the Computers/Contacts/Groups/Users views.

As a workaround, symlinking *View*.dll from /usr/lib/lat to ~/.lat/plugins works
for me. But the proper fix is certainly to move them in /usr/lib/lat/plugins.

Comment 1 Paul Howarth 2007-03-17 13:29:53 UTC
Thanks for the report; the problem was due to our package overriding the install
directory for the main lat binary to put it in /usr/lib64/lat on x86_64 systems,
as upstream was putting it in /usr/lib/lat in older versions of lat. This had
the unfortunate side-effect of putting the plugins in the wrong place.

Happily, the upstream Makefile now installs the main lat binary in the right
place itself, so there's no need for the override, and the plugins now go to the
right place.

This should be fixed in lat-1.2.2-2.fc6

Comment 2 Fabrice Bellet 2007-03-19 15:35:43 UTC
it works for me. thanks!


Note You need to log in before you can comment on or make changes to this bug.