ngcpcfg

Commit Graph

Author	SHA1	Message	Date
Guillem Jover	631c42c8ef	TT#61954 Update copyright years Change-Id: I3cb7889a3cd86167ae4b3dfaaaf7abeebc71004d	7 years ago
Guillem Jover	127ab70dec	TT#61954 Reorder and reformat copyright File stanzas As per the spec, the more general one should come first, and the more specific ones latter. Expand © to Copyright too, and place file entries on their own line. Change-Id: Ic0832aa19c76a500b827e06ff7e4af581e9e792b	7 years ago
Michael Prokop	08f68c829b	MT#22361 Remember file permissions through pre-commit hook + restore-permissions helper script Git doesn't track file permissions (except for the executable flag). For sensitive data (like the 'ssl' directory and file 'constants.yml' with passwords included) we've to prevent non-root users from accessing those files. hooks/pre-commit is inspired and based on the implementation as present in etckeeper (and luckily we're license compatible) and takes care of storing the file permissions inside file /etc/ngcp-config/.ngcpcfg_perms. The restore-permissions helper script takes care of restoring the permissions after cloning the ngcpcfg repository via ngcpcfg itself (being actions decrypt, pull (PRO-only) + initialise (PRO-only)). It can be executed manually as well via `usr/share/ngcp-ngcpcfg/helper/restore-permissions /etc/ngcp-config/` (or wherever the according ngcpcfg repository is placed at). Regarding the commit integration: git(1) itself doesn't track file permissions, so we can't detect changes to file permissions using git itself. Our new pre-commit hook records file permissions via the .ngcpcfg_perms file. Now by just invoking it during 'ngcpcfg commit' time we can ensure that even if there have been any file permission changes in the working directory the file .ngcpcfg_perms is then up2date and committed. JFTR: The solution via the git pre-commit hook ensures that no matter whether you're using 'ngcpcfg commit …' or 'git commit …' you always get the file permissions handled via .ngcpcfg_perms. Now if you want to change file permissions in a clean working directory and commit without using 'ngcpcfg commit' but directly via git itself then you've to use 'git commit --allow-empty ...' and thanks to the pre-commit hook the file .ngcpcfg_perms will still be up2date. Change-Id: I84d608585c626b52112ff649893e232e441c59d8	10 years ago
Michael Prokop	c409008799	MT#16473 Convert debian/copyright to machine-readable format See https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Converted via update-copyright. Change-Id: I997aa46419199d8203aba728387b6d3468344af8	11 years ago
Michael Prokop	9eb945734a	MT#15937 debian/copyright: adjust copyright year information Change-Id: I870a7f2296bc742b827dd60c1a8d8fcd4f09103f	11 years ago
Victor Seva	86ae8e8d99	MT#7141 upgrade package to 3.0 style	12 years ago
Michael Prokop	3436c08361	Initial checkin	13 years ago

7 Commits (1054cb4d74dfd43912a4fe7fc64c7e19f0253069)