Date: Sun, 30 Dec 2007 23:55:02 -0200 From: Marcus Alves Grando <mnag@FreeBSD.org> To: Jeremy Messenger <mezz7@cox.net> Cc: ports@freebsd.org, Maxim Khitrov <mkhitrov@gmail.com>, Yuri Pankov <yuri.pankov@gmail.com> Subject: Re: sqlite3 - any plans to update? Message-ID: <47784BF6.5010601@FreeBSD.org> In-Reply-To: <op.t3333gwg9aq2h7@mezz.mezzweb.com> References: <20071229115014.GH57401@darklight.org.ru> <26ddd1750712290925h7c5b698dn46cab08684be0337@mail.gmail.com> <26ddd1750712291135v22b015ct7a24279cd98583f4@mail.gmail.com> <op.t3333gwg9aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Messenger escreveu: > On Sat, 29 Dec 2007 13:35:43 -0600, Maxim Khitrov <mkhitrov@gmail.com> > wrote: > >> On Dec 29, 2007 12:25 PM, Maxim Khitrov <mkhitrov@gmail.com> wrote: >>> On Dec 29, 2007 6:50 AM, Yuri Pankov <yuri.pankov@gmail.com> wrote: >>> > Hi, >>> > >>> > First of all - why this is a question and not PR with patch to >>> update - >>> > there are too many dependant ports which I have no way to test and >>> > current stable version is 3.5.4, which isn't minor modification (I >>> > think). And I'm getting spammed by bogofilter trying to convince me to >>> > update sqlite to at least version 3.4.2. >>> > >>> > So, are there some showstoppers or is it just ETIME & EHOLIDAYS? :-) >>> > >>> > >>> > TIA, >>> > Yuri >>> >>> I e-mailed the maintainer as well as portmgr@. No response from >>> maintainer, but Pav Lucistnik suggested that I prepare the update then >>> wait 2 weeks to allow anyone other than the maintainer (assuming that >>> he is MIA) to commit. I even started looking at it, but I have about >>> 10 other things I need to be working on. I'll see if it's a simple >>> case of updating the makefile and distinfo. If not, it would probably >>> be best if someone more familiar with sqlite (and ports) internals >>> handle the update. >>> >>> - Max >> >> I was able to build the new version, and it seems to be working. >> However, there were some major changes made (to sqlite and the port >> itself) and I wouldn't recommend using my version in a production >> environment. I had to get rid of the FTS options because those patches >> didn't work anymore. In any case, the port has to be updated for FTS >> 3. I don't have the time right now to come up with something new. >> Also, it seems that this version now requires TCL 8.4 even when >> building without TCLWRAPPER. Not sure why it does this, the >> --disable-tcl switch is passed to configure but compilation still >> fails without tcl installed. >> >> Anyway, download the new port from the url below and extract it in >> /usr/ports/databases. It will create sqlite35 and sqlite35-threads >> directories. Other than the removal of FTS and new dependency on TCL >> 8.4, everything else should be the same as for sqlite3 port. Test it >> out, see if it works for you. If no one has any problems with it then >> maybe it can be added to the ports tree, but someone else will need to >> maintain it. I don't have much time these days, unfortunately. >> >> URL: http://mxwerx.com/sqlite35.tar.gz > > http://www.sqlite.org/34to35.html > =========================================== > 6.0 Summary > > The transition from SQLite version 3.4.2 to 3.5.0 is a major change. > Every source code file in the SQLite core had to be modified, some > extensively. And the change introduced some minor incompatibilities in > the C interface. But we feel that the benefits of the transition from > 3.4.2 to 3.5.0 far outweigh the pain of porting. The new VFS layer is > now well-defined and stable and should simplify future customizations. > The VFS layer, and the separable memory allocator and mutex subsystems > allow a standard SQLite source code amalgamation to be used in an > embedded project without change, greatly simplifying configuration > management. And the resulting system is much more tolerant of highly > threaded designs. > =========================================== > > Someone might need to create sqlite35 instead of update to 3.5.x in > sqlite3. If it can be done to update 3.5.x in sqlite3, then I would hold > on until ports tree is complete unfreeze (still thaw). > > Cheers, > Mezz I'll create a sqlite34 and sqlite35 port for update of 3.4 and new 3.5 port, but because of many changes in sqlite i can't do that now, i'll wait ports slush. Wait a few more days, i don't forget of sqlite. Regards > >> - Max > > -- Marcus Alves Grando marcus(at)sbh.eng.br | Personal mnag(at)FreeBSD.org | FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47784BF6.5010601>