On Tue, Aug 31, 2010 at 10:51, Richard Hipp <d...@sqlite.org> wrote: > My suggestion is that you make a copy of the os_unix.c source file (call it > chromium_vfs.c or anything else that you like) and apply your edits to that > copy. Since you started with an exact copy of the original os_unix.c > source > file, your copy will all the internal utilities and mechanisms as > os_unix.c. You can use all those internal mechanism as much as you want. > Then compile your customized VFS separately and add it to SQLite at > start-time using sqlite3_vfs_register(). > > Why won't that work for you?
It effectively forks os_unix.c, which makes upgrades of SQLite equally painful to the current state. The above solution offers no advantage over the current state of our bundled SQLite copy. I'd like to stay as close to upstream as possible, because then we can update very easily. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
