BIND 10 #1982: sqlite database upgrade during make install

[BIND 10 Development]

#1982: sqlite database upgrade during make install
-------------------------------------+-------------------------------------
                   Reporter:  cas    |                 Owner:  UnAssigned
                       Type:         |                Status:  new
  enhancement                        |             Milestone:  New Tasks
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  build  |           Sub-Project:  Core
  system                             |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [ticket:1982 cas]:
 > I'm trying to build new RPM packages for BIND 10 20120517.
 >
 > Even though I'm installing into a sandbox directory (with make
 DESTDIR=/sandbox install), the makeinstall script stops with an error that
 my sqlite DB in /usr/local/var/bind10-devel/zone.sqlite is of version 1
 and I need to upgrade it to version 2. That file is not in the sandbox and
 should be of no concern when building packages.
 >
 > I would prefer if the upgrade check (and maybe even the automatic
 upgrade of the database) is done when BIND 10 is started, not during the
 install script.

 We do have a plan (or at least an idea) to make the check happen at
 start up time: #1842

 Regarding the installation time check, I personally think it's still
 useful.  If a careless user just overrides the system with a new
 version that requires incompatible DB schema and restarts BIND 10, the
 service will effectively stop until the DB is upgraded, regardless
 whether the user has to do it by hand or some start up part of BIND 10
 does it automatically.  It's probably not ideal if that takes time
 (e.g., tens of minutes).  "Better safe than sorry".

 But I agree that the current behavior where it checks the installed DB
 file just to make an independent package, and that we should at least
 solve that problem sooner.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1982#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development