apr-util-1.2.8 (a dependency of subversion) has USE-flags "sqlite" and "slite3" for sqlite versions 2 and 3 respectively. If sqlite-3 is already installed, it somewhere sets the "sqlite" flag which is picked up when merging new apps. Thus "emerge --update --deep --newuse" will pull in a slotted version of sqlite-2 next to sqlite-3 if the latter is already installed. Changing the USE-flags to "sqlite2" and "sqlite" respectively would be preferable as 3.3.x is the current active release series. Reproducible: Always
If you wish this changed, take it to gentoo-dev ML. Shuffling with the use flags meaning sucks, means a lot of work for not exactly apparent gain. If you dislike this, then use package.keywords, that's what it's for. sqlite - Adds support for sqlite - embedded sql database sqlite3 - Adds support for sqlite3 - embedded sql database
That's what I did, employing package.keywords. Nonetheless, having a package duplicated for no apparent reaons sucks as well. Everyone bitten by this has to remove sqlite-2 manually and recompile apr-util with the appropiate use-flags, i.e. everyone using subversion. Otherwise there's another outdated package lingering around ... not to nice either.
> If sqlite-3 is already installed, it > somewhere sets the "sqlite" flag which is picked up when merging new apps. This has not been the default behaviour since portage 2.1, released more than one year ago. Either you're using a heavily outdated version, or you're messing with portage variables that you shouldn't (USE_ORDER).
Messing, make.conf has: # # portage-2.1 fix # see: http://forums.gentoo.org/viewtopic-t-446812-postdays-0-postorder-asc-start-25.html # USE_ORDER="env:pkg:conf:auto:defaults"
Well, then remove the line from your make.conf; the defaults are USE_ORDER="env:pkg:conf:defaults:pkginternal" w/ anything starting from 2.1
BTW, 23 packages have sqlite3 use flag ATM; sounds like changing it would just cause lots of confusion.
