Bug 24608 - ck does not respect multilib
Summary: ck does not respect multilib
Status: NEW
Alias: None
Product: ConsoleKit
Classification: Unclassified
Component: Daemon (show other bugs)
Version: unspecified
Hardware: All All
: medium trivial
Assignee: william.jon.mccann
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-18 14:37 UTC by Gilles Dartiguelongue
Modified: 2010-01-31 01:29 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
0001-respect-multilib.patch (4.28 KB, patch)
2009-10-18 14:37 UTC, Gilles Dartiguelongue
Details | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Gilles Dartiguelongue 2009-10-18 14:37:44 UTC
Created attachment 30542 [details] [review]
0001-respect-multilib.patch

prefix + lib/ = libdir, see attached patch.

actually I think this is still not the proper place but it's a better default than not taking multilib into account at all. Thanks for considering.
Comment 1 william.jon.mccann 2010-01-28 15:38:50 UTC
This used to be this way but we changed it due to some problems Kay found.  What problems does the current way cause?

commit 3c8db75b2ffdba1627a7030a4b57ce7ee8e474f2
Author: William Jon McCann <jmccann@redhat.com>
Date:   Fri Apr 18 16:11:59 2008 -0400

    install scripts into $(prefix)/lib instead of $libdir
    
    We don't want scripts going into lib64...
Comment 2 Gilles Dartiguelongue 2010-01-31 01:29:12 UTC
It causes no real problem, it's just that some of us get QA warnings when a package installs stuff in /usr/lib while it should have gone in /usr/lib64 (non respected autotools config switch, ...). Also admittedly shell scripts are not arch dependent, that's why I think they shouldn't be in /usr/lib* at all.

In any case, I'd be curious to know what were the problems when scripts were in /usr/lib64 since I've had no user report about anything broken yet.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.