Re: [Tiki-devel] God, save us from secdb and help on tarball checking

I think the way secdb works is that every install adds or updates the new files into the database. So if you had several older versions of Tiki installed in the past, legacy files show up as legacy, with a legitimate check. Will your changes preserve this behaviour?

Brendan



> On Aug 23, 2021, at 12:24 PM, Fabio Montefuscolo <[email protected]> wrote:
> 
> Hello all!
> 
> I am coming back with the proposal of having secdb as regular text file, compatible to md5sum linux tool.
> 
> Actually, what I do to test tarballs other than running the installer is getting the md5sum compatible file. To that, I have to load the secdb into MySQL and then dump it again. More precisely
> cat db/tiki-secdb_23.0_mysql.sql  | docker-compose exec -T db mysql -ptikiwiki tikiwiki
> echo "select concat(md5_value, '  ', filename) from tiki_secdb;" | docker-compose exec -T db mysql -ptikiwiki tikiwiki  -N -s > ../calc
> md5sum -c ../calc
> 
> I wonder if we can reduce the steps above to a single step and at the same time, we free the user from loading 5,1Mb table into MySQL. If for some reason thinks his checksum file is corrupted, he always can grab a fresh one from our gitlab. The latest one for 23.0 for example is https://gitlab.com/tikiwiki/tiki/-/raw/tags/23.0/db/tiki-secdb_23.0_mysql.sql <https://gitlab.com/tikiwiki/tiki/-/raw/tags/23.0/db/tiki-secdb_23.0_mysql.sql>.
> 
> I agree it is good to have a checking tool, but not in MySQL, that impacts the installation process and also the backup process.
> 
> If windows is a concern, we can find a solution to check that on Windows.
> 
> What do you think?
> 
> Thanks
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel