historic database addition to git
Locked
historic database addition to git
 
|
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 _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: historic database addition to git
|
|
For me, this way is clean and understable.
Yes, everyone will download all, but note that 'tests' and 'project' are not packaged in release tarballs.
Note : It's Holiday time for Marcel until 2 weeks.
Gilles Caulier 2011/6/27 Francesco Riosa <[hidden email]> I'm planning to add a minimal collection with related databases to _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: historic database addition to git
|
|
http://quickgit.kde.org/?p=digikam.git&a=commit&h=4f9552478693752c00b0aebab4cde043c9df8ecf Committed in master, under tests/databases/ since it would make no sense to cherry-pick it later, and it's stuff that can be useful for others too. The dumps need to be re-done but it's too late right now On a related note migration from sqlite to mysql should be in shape again, there are just some indexes which are not created (and no bug report because bugzilla is down ): I'll be on holiday July 2-10 and desperate (but present) July 11-15 Francesco R. On 06/27/11 13:07, Gilles Caulier wrote: > For me, this way is clean and understable. > > Yes, everyone will download all, but note that 'tests' and 'project' are > not packaged in release tarballs. > > Note : It's Holiday time for Marcel until 2 weeks. > > Gilles Caulier > > 2011/6/27 Francesco Riosa <[hidden email] > <mailto:[hidden email]>> > > 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 Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
«
Return to digikam-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |