[Qa-debsources] patch-tracker DB schema

[Orestis Ioannou]

Heya,

Following Here is a proposed DB schema for the patch tracker:


++++++++++++++++++
|||||Patches||||||
++++++++++++++++++
|     id         |
+----------------+
|     file_id    |
+----------------+
|   package_id   |
+----------------+
|  file deltas   |
+----------------+

The file_id points to the file in debian/patches.

Maybe file deltas are useless, the idea behind storing them is that we
could possibly in the future have the following use case:

    - Which are the patches that have been applied to this 'file' in
this 'package'

They can be a JSONB object.

I propose another two modifications for the package table:
- store the patches format
- store the SHA256 of the orig.tar.gz. This was something in the old
patch tracker and I think its usefull for upstreams (Easily find out if
maintainer changed something).

In the use stories (in doc/patch-tracker.txt) I thought of the
possibility of proposing to download and view a diff of the orig.tar.gz.
With the proposed schema this is not possible. Are we maintaining this?
I guess to do this we will need to store the diff while we extract the
package.

Cheers,

Orestis

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/qa-debsources/attachments/20160118/1821d570/attachment.sig>