On Sat, Jan 11, 2014 at 1:24 PM, Jan Nijtmans <jan.nijtm...@gmail.com>wrote:
> 2014/1/4 James Turner <ja...@calminferno.net>: > > > I won't begin to tell you how to develop fossil but I do want to throw > > out there that OpenBSD has been providing fossil with > > --disable-internal-sqlite via it's ports tree and packages fairly > > successfully (and with 'fossil sqlite3' support) for the last year+. > > I re-enabled "fossil sqlite3" again in the "branch-1.28" branch: > My guess is that most package maintainers will re-enable > it anyway. It's easy enough, but I want to make your > work easier, not more difficult. For trunk, there's still > more than enough time to think how this should be > fixed the 'correct' way, which satisfies everyone (I hope). > I *still* haven't sent out that message / warning yet, but I'm getting closer. Have info now for: CentOS (and Scientific Linux), Cygwin, Debian (and Ubuntu), Fedora, FreeBSD, Gentoo (and Sabayon), NetBSD, OpenBSD (can be skipped however), openSUSE, Slackware. I haven't looked up the Solaris variants yet, nor the "other" Linux and BSD distros (Linux: Arch, Mageia, Manjaro, Puppy; BSD: Dragonfly, Ghost, PC-BSD). The message will take into account that a 1.28 release will (apparently) permit --disable-internal-sqlite, but that it is still subject to disabling (and/or may already be disabled?) for development versions / trunk and therefore for a future 1.29 release. (I have to lookit the sources online to verify this before I say it, however.) Just a heads up that no, I haven't forgotten or given up. I'm just slow. Joseph
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
