On 2014/04/14 15:52, Fabian Raetz wrote: > > - what do users need to do for the upgrade - is it just "log file format > > change" or also "database format change"? we will need to document the > > steps needed, and probably add @ask-update and an faq/current.html section. > > Only the log file format has changed.
OK, so I suppose we need to identify whether the dependent ports use transactions or not to figure out whether people need to follow the "If the application has a Berkeley DB transactional environment, and the log files need upgrading but the databases do not, the application may be installed in the field using the following steps" instructions or just update.. > Not sure if we should note the db_codegen -> db_sql replacement. > > http://download.oracle.com/otndocs/products/berkeleydb/html/4.7.html > http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_4_8_0.html > > Berkeley DB introduces a new utility named db_sql which replaces > db_codegen. > Similar to db_codegen, db_sql accepts an input file with DDL statements > and > generates a Berkeley DB application using the C API that creates and > performs > CRUD operations on the defined tables. The developer can then use that > code > as a basis for further application development. Not necessary I think. > Do i have to bump SHARED_LIBS? In ${WRKBUILD}/shared_libs.log the versions > stayed the same. If there is an API/ABI change then a bump is required, if no change then bump not required, if in doubt then bump. More details on this at http://www.openbsd.org/faq/ports/specialtopics.html#SharedLibs > If not, here is my proposed diff: I'll try and have a better look at this, and do some tests on dependencies etc, sometime over the next week. > REVISION-main = 0 .. > +REVISION-java = 0 > REVISION-tcl = 0 Updating to a newer version means The REVISION-* lines should be removed.
