[Dbconfig-common-devel] first post, TODO and the road ahead

[sean finney]

--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

i've finally gotten around to creating this list, which will hopefully
at some point serve as a discussion area for matters relating to
the development of the database app policy as well as the package=20
implementing the resulting decisions.

currently, these are the contents of my todo list:

- finish postgresql support.  support is basically there now, but the
  dumping and recovering still needs to be implemented and tested.
- generalized interface for multi-dbtype applications.  again, almost
  there.
- template translations.  maybe it's still a bit pre-mature, as the
  templates are not *quite* stabilized yet and i'd feel horrible
  wasting the time of our good friends the translators.
- oliver elphick's idea of having a generated list of configurations.
  support for this isn't too much of a stretch. instead of caching
  hostnames in the debconf hosts, we could store DSNs which could
  later be broken down when written to config files.  the caching of
  responses is already partly done, though it's not being stored in
  a file and isn't global to all db packages yet.
- better error handling and notification.  some testing will probably
  flush out what needs to be done.
- purge password and upgrade responses from debconf
- give local admin the choice of caching or not caching passwords
- tcp/ip to honor port setting (requires hacking or replacing wwwconfig)
- don't send passwords on the cmdline (ditto)
- tcp/ip over ssl for mysql (ditto)
- making some debconf responses shared globally (like remote host)
- include file generator.  (for perl/php/foo apps that want to include
  settings easily).  some preliminary work done outside of cvs.  i think
  we'd need to use ucf to help manage the extra layer of config abstraction.

the most up to date version of the todo list can be found in the
cvs tree for the package, or in /usr/share/doc/dbconfig-common on
installed systems.

things not mentioned above:

- i'll also shortly be uploading the latest version of dbconfig-common (0.8=
)=20
  to experimental.
- this mailing list now recieves logs of cvs updates
- testing is still needed, primarily for the postgresql flavored
  scripts, but also digging for errors in corner cases and finding
  other places where the set of scripts can be made more robust.


	sean

--

--Dxnq1zWXvFF0Q93v
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFByHsbynjLPm522B0RAgPDAJsEyloU/6wtyVN0ufrW3wUc3YLEVACfcdov
ttJ8gD1aRvgCDKzcIQ5sKqM=
=xrid
-----END PGP SIGNATURE-----

--Dxnq1zWXvFF0Q93v--