Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 191686 - apr-util: sqlite 2 shouldn't be enabled on sqlite3-flag
Summary: apr-util: sqlite 2 shouldn't be enabled on sqlite3-flag
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Apache Team - Bugzilla Reports
URL:
Whiteboard:
Keywords:
: 350929 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-09-08 12:35 UTC by Hanno Böck
Modified: 2011-04-16 17:26 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hanno Böck gentoo-dev 2007-09-08 12:35:24 UTC
It's probably a similar case than our earlier gtk1/2-problem.

From my understanding, USE="sqlite sqlite3" means, enable sqlite support if available and use sqlite3 if both 2 and 3 are available.

Thus, apr-util should have something like this:
DEPEND="sqlite? ( sqlite3? ( =dev-db/sqlite-3* )
!sqlite3? ( =dev-db/sqlite-2* ) )"
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-09-08 12:47:47 UTC
Uhm, no? You generally can't enable gtk+1 *and* gtk+2 at the same time, because the app either supports one or the other. So, this is completely different. 

If you dislike how's it handled and have a better, consistent and treewide solution, take it to gentoo-dev ML. Disabling feature that people need just because you dislike it doesn't fly much. Plus, the flag description is pretty clear about what it means.

# euse -i sqlite3
global use flags (searching: sqlite3)
************************************************************
[+ C  ] sqlite3 - Adds support for sqlite3 - embedded sql database
Comment 2 Benedikt Böhm (RETIRED) gentoo-dev 2007-09-09 07:16:43 UTC
sqlite = 2.x
sqlite3 = 3.x
Comment 3 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev 2011-04-16 17:26:23 UTC
*** Bug 350929 has been marked as a duplicate of this bug. ***