Bug 362647

Summary:	app-portage/eix rename USE flag from "sqlite" to "sqlite3"
Product:	Portage Development	Reporter:	Marcin Mirosław <bug>
Component:	Third-Party Tools	Assignee:	Martin Väth <martin>
Status:	RESOLVED INVALID
Severity:	minor	CC:	darkside
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Marcin Mirosław 2011-04-08 18:01:09 UTC

eix has USE flag "sqlite" it suggest eix can use sqlite based cache. It can be a little misleading, because portage can use sqlite-3. Imho use flag should be changed do "sqlite3" and dependency changed a little:

-sqlite? ( >=dev-db/sqlite-3 )
+sqlite3? ( >=dev-db/sqlite:3 )

Reproducible: Always

Comment 1 Jeremy Olexa (darkside) (RETIRED) archtester

2011-04-08 18:08:18 UTC

It is abit ambiguous. I agree. But you can see that people are doing it both ways.

% quse -D sqlite
 global:sqlite: Adds support for sqlite - embedded sql database
 local:sqlite:app-admin/ulogd: Build SQLITE3 output plugin to save packets in an sqlite database.
 local:sqlite:app-portage/eix: Compile in support for portage's sqlite backend; to actually use it you need additional configuration of portage and eix
 local:sqlite:dev-scheme/bigloo: Use the system-wide dev-db/sqlite
 local:sqlite:net-im/ekg2: Support logging messages into SQLite2 database. If 'sqlite3' is set too, it will be used instead.
 local:sqlite:net-p2p/gnunet: enable sqlite database backend

% quse -D sqlite3
 global:sqlite3: Adds support for sqlite3 - embedded sql database
 local:sqlite3:net-im/ekg2: Support logging messages into SQLite3 database. If 'sqlite' is set too, SQLite3 will be used.

Comment 2 Michał Górny archtester

2011-04-16 07:00:21 UTC

Due to bug #363805 [1], closing this as INVALID.

[1] http://bugs.gentoo.org/363805