GSoC project discussions

[Ralf Habacker]

Am 12.05.20 um 10:08 schrieb Ralf Habacker:
> Am 09.05.20 um 15:36 schrieb Prasun Kumar:
>> Hi everyone,
>> As mentioned in the project proposal, one of the major tasks is to 
>> replace the text bankdata files with an SQLite database. Currently, 
>> KtoBlzCheck comes with one data file which is valid at the time of 
>> release. Then during building, a file valid at the current date is 
>> downloaded from the bank and converted into a file suitable for the 
>> library. _So, when migrating to an SQLite DB, how should this DB file 
>> be distributed and updated?_
> 
> A Qt/KDE-based api is available for this store to access data from this 
> store (see https://api.kde.org/frameworks/knewstuff/html/index.html), 
> which is probably not ideal for non KDE applications like aqbanking or 
> GnuCash. Qt is already used by aqbanking, but KDE libraries are not and 
> GnuCash uses gnome libraries.

One step should be to separate releasing the data from the software. The 
current cmake system provides some cmake targets for package releases.

~/src/ktoblzcheck-build> make help | grep package
... package_source
... package

where 'package_source' stands for the generation of a source tarball for 
a particular version at 
https://sourceforge.net/projects/ktoblzcheck/files/ and 'package' stands 
for the generation of a binary package (currently used for the web 
services mentioned at http://ktoblzcheck.sourceforge.net/).
The `package_source' target would need to be modified to not contain the 
bank data files, and an additional target called `package_data' is added 
to create the package containing the bank data files to be released.

The entire process for releasing new bank data files (based on 
https://sourceforge.net/p/ktoblzcheck/code/ci/master/tree/README.md) 
would then be as follows:

git-clone ssh://xxx@git.code.sf.net/p/ktoblzcheck/code ktoblzcheck
mkdir ktoblzcheck-build
cd ktoblzcheck-build
cmake ../ktoblzcheck -DINSTALL_RAW_BANKDATA_FILE=1 
-DINSTALL_SEPA_BANKDATA_FILE=1
make
make package_data


This would create a file named ktoblzcheck-data-<date>.tar.xz, which can 
be uploaded by a project member to the download area 
https://sourceforge.net/projects/ktoblzcheck/files/

The whole thing could be scripted to have an automatic update process. 
The upload can be done with scp, for example

eval `ssh-agent`
ssh-add <private-ssh-key-to-access-sf>
scp ktoblzcheck-data-<date>.tar.xz ...

Regards
Ralf