In subversion 1.6.6 it wasn't made mandatory to have a threadsafe sqlite if apr is compiled without threadsafety. Can we drop the [threadsafe] requirement ? Not sure if there's an easy test to see if apr was compiled with/without threads to allow this though.
Why would you want to have thread-unsafe SQLite?
Because I'm using gentoo prefix on a platform which doesn't have threads.
bump. 1.6.12 is out. Is there an easy test to see if dev-libs/apr is built threadsafe ?
Prefix folks.... Can we add another line to the ebuild that does... !m68k-mint ( >=dev-db/sqlite-3.4[threadsafe] ) m68k-mint ( >=dev-db/sqlite-3.4 ) for now ??
fine with me if it's still in our overlay
ping prefix folks - yes it's still in our overlay....
ping prefix folks again, can we make the change here ? thanks.
sorry, applied. This bug is not assigned to prefix team, hence it slipped under the radar
This is being considered for 1.6.17-r1; my apologies for the lack of action on this so far.
+*subversion-1.6.17-r1 (18 Aug 2011) + + 18 Aug 2011; Tony Vroon <chainsaw@gentoo.org> +files/47_mod_dav_svn.conf, + +files/80subversion-extras, +subversion-1.6.17-r1.ebuild, + +files/svnserve.initd2: + Cut down extraneous einfo as requested by Gokdeniz Karadag in bug #268633. + Removed USE=threadsafe requirement for sqlite as per Alan Hourihane in bug + #323951. Stop use of --chuid in init script as per Michael Mair-Keimberger in + bug #377781. Removed overengineered testing facilities; unmaintainable in + current state. Moved remaining inline configuration files to FILESDIR. + Removed custom inline print function.
