[Piuparts-devel] LogDB refactoring

Dave Steele dsteele at gmail.com
Fri May 24 22:46:54 UTC 2013


> * get that heavily discussed branch from dave into shape

See log-refactor (13) for an idea of what would be my next step in problem
integration - isolate path and filename info into LogDB, in preparation for
a common log/bug/problem abstract superclass:

bbba068 packagesdb - Remove obsolete calls from LogDB.
26172ba packagedb - Remove all log path references from PackagesDB.
9a88a4c packagesdb - Remove unnecessary logdb.remove() calls from
PackagesDB.
5137773 packagesdb - Replace LogDB create() with createlog(), which doesn't
need path.
87afca2 packagesdb - PackagesDB get log file state without need for path
info.
a7d30c8 packagesdb - LogDB returns directory and testing state of package.
b895623 packagesdb - Collect log files in LogDB at initialization.
ac83267 packagesdb - Move log subdirectory creation from PackagesDB to
LogDB.
91e2b7c packagesdb - Add directory and log states to LogDB.
29d769d packagesdb - Add 'prefix' to LogDB
73c5fa6 packagesdb - Refactor package/version filename validation to LogDB.
80e8414 packagesdb - Remove obsolete states from PackagesDB.
0a4c208 packagesdb - Remove get_time().

Part of this plan would be to merge report_problem_integration now, as an
incremental improvement.

Note that log-refactor is currently unrunnable. More consideration is
needed for recycle (life becomes very simple if you don't need a "recycle
mode" flag).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20130524/104a1420/attachment.html>


More information about the Piuparts-devel mailing list