| Summary: | dev-liba/apr-util make sqlite USE flag consistent | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | C. Wijtmans <cj.wijtmans> |
| Component: | New packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | minor | CC: | jmbsvicetto |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
C. Wijtmans
2011-01-07 05:27:53 UTC
Commenting on the chromium part of this: the sqlite use flag is global with a specific meaning. global use flags (searching: sqlite) ************************************************************ [- ] sqlite - Adds support for sqlite - embedded sql database Chromium's system-sqlite means something slightly different; chromium is built with sqlite either way, but it uses a bundled copy by default. This use flag is consistent with other packages that bundle sqlite. local use flags (searching: system-sqlite) ************************************************************ [- ] system-sqlite (mail-client/thunderbird): Use the system-wide dev-db/sqlite installation with secure-delete enabled [- ] system-sqlite (net-libs/xulrunner): Use the system-wide dev-db/sqlite installation with secure-delete enabled [- ] system-sqlite (www-client/chromium): Use the system-wide dev-db/sqlite installation with secure-delete enabled [- ] system-sqlite (www-client/firefox): Use the system-wide dev-db/sqlite installation with secure-delete enabled [- ] system-sqlite (www-client/icecat): Use the system-wide dev-db/sqlite installation with secure-delete enabled [- ] system-sqlite (www-client/seamonkey): Use the system-wide dev-db/sqlite installation with secure-delete enabled [- ] system-sqlite (x11-plugins/enigmail): Use the system-wide dev-db/sqlite installation with secure-delete enabled (In reply to comment #1) > Chromium's system-sqlite means something slightly different; chromium is built > with sqlite either way, but it uses a bundled copy by default. This use flag is > consistent with other packages that bundle sqlite. Does this mean sqlite can still be disabled by -sqlite even if having system-sqlite? Does this make sense? (In reply to comment #2) > (In reply to comment #1) > > Chromium's system-sqlite means something slightly different; chromium is built > > with sqlite either way, but it uses a bundled copy by default. This use flag is > > consistent with other packages that bundle sqlite. > > Does this mean sqlite can still be disabled by -sqlite even if having > system-sqlite? Does this make sense? No. You simply can't disable sqlite for Chromium. The system-sqlite is used to allow the user to choose the system's sqlite or the bundled one. IIRC, the mozilla herd has the same use flag for firefox ebuilds. I believe this bug should be closed as WONTFIX, but I'll let the chromium and mozilla teams express their opinion. Hi, What about the apr-util package? it is still linked/built against sqlite-2.8 now even if i had specified sqlite3, which is the same as default sqlite. Can it be renamed to sqlite2, for consistency? (In reply to comment #4) > Hi, > > What about the apr-util package? it is still linked/built against sqlite-2.8 > now even if i had specified sqlite3, which is the same as default sqlite. Can > it be renamed to sqlite2, for consistency? If you check http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-libs/apr-util/apr-util-1.3.9-r1.ebuild?revision=1.1&view=markup , you'll see the ebuild has sqlite and sqlite3 use flags. Anyway, closing this one. I think you are looking for an easy way out or dont understand me. As i have said before; When compiling apr-util package with sqlite USE flag, it compiles with sqlite-2.8. On my system i have sqlite 3, so in my use flags i specified sqlite3. Now it pulled in both sqlite2.8 and sqlite3, and it is still linked against sqlite2.8. Now to fix this, my proposal; rename sqlite3 to sqlite2 to depend on sqlite2.8. (its the other way around) The sqlite/sqlite3 flags on apr-util are a bit strange; sending this to the apache herd since this has nothing to do with Chromium. *** This bug has been marked as a duplicate of bug 191686 *** |