| Summary: | ck does not respect multilib | ||
|---|---|---|---|
| Product: | ConsoleKit | Reporter: | Gilles Dartiguelongue <gilles.dartiguelongue> |
| Component: | Daemon | Assignee: | william.jon.mccann |
| Status: | NEW --- | QA Contact: | |
| Severity: | trivial | ||
| Priority: | medium | CC: | freedesktop-bugs |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | 0001-respect-multilib.patch | ||
|
Description
Gilles Dartiguelongue
2009-10-18 14:37:44 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... 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.