sqlite-3.1.3 provided on OS X 1.4 with developer tools 2.1, possibly earlier. Causes a conflict when trying
to emerge sqlite; should be added to package.provided.
Steps to Reproduce:
>>> Completed installing sqlite-3.2.2 into /var/tmp/portage/sqlite-3.2.2/image/
* checking 12 files for package collisions
existing file /usr/bin/sqlite3 is not owned by this package
existing file /usr/include/sqlite3.h is not owned by this package
existing file /usr/lib/libsqlite184.108.40.206.dylib is not owned by this package
* spent 0.00536108016968 seconds checking for file collisions
* This package is blocked because it wants to overwrite
* files belonging to other packages (see messages above).
* If you have no clue what this is all about report it
* as a bug for this package on http://bugs.gentoo.org
Provided version seems to fail during configuration of other packages. There seems to be no 'sqlite3.pc'
file anywhere in the filesystem. Error output from lighttpd's configuration:
checking for sqlite3... Package sqlite3 was not found in the pkg-config search path. Perhaps you should
add the directory containing `sqlite3.pc' to the PKG_CONFIG_PATH environment variable No package
configure: error: Library requirements (sqlite3) not met; consider adjusting the PKG_CONFIG_PATH
environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.
I wonder if this has anything to do with the SQLite bug 1026: http://www.sqlite.org/cvstrac/tktview?
Might be related, but if the sqlite.pc file is not in the system, it is not
going to work. If I recall correctly pkg-config isn't provided with OSX, so it
seems normal to me that there isn't a .pc file for any system provided package,
hence we cannot add sqlite-3.0.8 to the package.provided file.
I'm not sure on this, but I thought Apple uses SQLite for spotlight, so
overwriting the system install might break things. You can push your luck by
disabling the collision-protect feature for this package, no guarantees though.
I'm closing this bug because IMHO this can't be fixed in the current setup of
Portage on OSX. It also implies a mask of sqlite.
Agreed. OS X uses sqlite for more than just spotlight. I forced the install and it hosed Safari along with
much of the rest of the operating system. Installing sqlite to /usr/local would be an appropriate "fix" by
providing all the functionality needed without conflicting with the files provided by OS X.
Using a different prefix is the solution we are looking forward to. That's the
reason why I closed the bug, because eventually it will be possible to install
it. Sorry to hear you trashed more than just spotlight...
It seems to make even more sense now that I masked sqlite ;)