[Digikam-devel] historic database addition to git

[Francesco Riosa]

I'm planning to add a minimal collection with related databases to 
sql/2.0 branch.

Rationale is to have an history of databases for each stable version and 
to test upgrades and code.

The problem is that (if I did understud it correctly) git fetch all 
branches and then apply the interested one, thus in practice forcing the 
download to everyone.

The numbers are about 1.1 MB of images that should not change ever, and 
200/300KB of databases dump, which git compress furter but can change as 
we do add things to test or whatever.

the structure would be something like the following (still not final yet):

drw    4096 ./19
-rw   27193 ./19/digikam.data.sql
-rw   31585 ./19/digikam4.db.data.sql
-rw   10671 ./19/digikam4.db.sql
-rw    1540 ./19/thumbnails-digikam.db.sql
-rw   14553 ./19/digikam.sql

drw    4096 ./20
-rw   27193 ./20/digikam.data.sql
-rw   31585 ./20/digikam4.db.data.sql
-rw   10671 ./20/digikam4.db.sql
-rw    1540 ./20/thumbnails-digikam.db.sql
-rw   14553 ./20/digikam.sql

-rw    1596 ./README
drw    4096 ./testimages
drw    4096 ./testimages/a2
-rw   99582 ./testimages/a2/Martian_face_viking.jpg
drw    4096 ./testimages/a2/pgf
drw    4096 ./testimages/a2/pgf/link
lrw      14 ./testimages/a2/pgf/link/foto001.pgf -> ../foto001.pgf
lrw      14 ./testimages/a2/pgf/link/lntofot	o.pgf -> ../foto001.pgf
-rw  496246 ./testimages/a2/pgf/foto001.pgf
drw    4096 ./testimages/a1
drw    4096 ./testimages/a1/png
-rw  119878 ./testimages/a1/png/snap001.png
-rw  119968 ./testimages/a1/png/snap002.png
drw    4096 ./testimages/a1/jpg
-rw   86838 ./testimages/a1/jpg/foto001bw.jpg
-rw  126893 ./testimages/a1/jpg/foto001.jpg

What do you think?

- Francesco Riosa