[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RFC: common database policy/infrastracture

hey all,

for those who weren't following the previous thread[1], i've come up with
a rough draft of a "best practices" document for database based
applications.  i'd greatly appreciate input, especially from the current
maintainers of database-using or database-server applications.  the draft
is available at:


also, after much discussion in this thread and privately
with joey hess, i think the best approach of the options discussed
would be to provide debconf questions in a single run-time dependency
package via the debconf REGISTER method.  it's not the best solution
(because of the risk of the questions being asked at postinst time),
but it should guaranteeably work, it's centralized, easily translatable,
and makes less work for folks who use it with their packages.

this package, "database-common", currently is only a collection of
normalized debconf templates.  this is very much a work in progress,
but i think at this point it's worthwhile to make sure there's sufficient
interest as well as possibly get some help :)

deb http://people.debian.org/~seanius/policy/examples/ ./
deb-src http://people.debian.org/~seanius/policy/examples/ ./

what's lacking:

- the blocks of code for the .*config, .*inst and .*rm files, which
  could be provided in a set of wrapper scripts to be sourced by the
  individual packages.
- a demonstration package using this
- possibly a debhelper-like package to automatically add these blocks
  of code 


- further amendments to the "best practices" document based on developer
- resulting changes in packaging from said changes
- templates for pgsql and other database setups (currently only some
  common templates and the mysql-centric ones)
- translations

so please, let me know what you think!  


[1] http://lists.debian.org/debian-devel/2004/10/msg00340.html


Attachment: signature.asc
Description: Digital signature

Reply to: