@MarkMLl: thanks you for the script: I will use it. In fact, until now, I was using a simple command line in a launcher:
gnome-terminal -e "bash -c '/home/.../.../lazarus --pcp=/home/.../.../Working_copies_all_projects/primary_config_path_files --log-enable=DBG_STATE, and so one...'"
@Martin_fr: thank you for reminding us of the basics of a Lazarus launch, "as it should be". I didn't know that lazarus.cfg was containing --pcp. And since I am currently satisfied with my configuration, I will continue as I do.
As I said, I will use the MarkLi method. Of course, I'm using Subversion. But, I want to trace the primary configuration files only for a real important change. However, among the roughly thirty files of the "--pcp", only 3 or 4 are always changing due to an IDE loading and subsequent compilations, nothing more. These files are too volatile for me: I only want to trace in SVN, big changes (first, a change of the Lazarus + fpc combo, and then the modification of the loaded packages. No more).
With MarkLi's script, I can try to remove from a real time SVN monitoring, all these files too volatile for my purposes, but nevertheless backup them with a YYYMMDD timestamp prefix (out of Subversion):
FILE_BACKUP=$(date +%Y%m%d)-backup
DIR_BACKUP=$CONFIG/backup
FULL_PATH_FILE_BACKUP=$DIR_BACKUP/$FILE_BACKUP
cd $CONFIG
tar -cvzf $FULL_PATH_FILE_BACKUP.tar.gz -T ./a_List_of_files_to_tar_and_zip.txt