* This should not be needed unless the software actually uses logrotate, which isn't common at all: logrotate? ( app-admin/logrotate ) * This looks tricky: # create fuzzyocr group for logging and hashing if use dbm || use logrotate ; then use amavis || enewgroup fuzzyocr fi Why don't you simply always support logging? The user would need to re- emerge the package simply to get logging working? Precisely what bug #198901 is about! * So you're not going to support logging stuff unless logrotate is installed? # Enable logfile if logrotate if use logrotate ; then Why don't you simply let the user decide, regardless of USE flags? * Can't you use `chmod g+s' on the directory? Doesn't the software create the file when it needs it? if [ ! -e /var/log/FuzzyOcr.log ]; then insinto /var/log newins /dev/null FuzzyOcr.log if use amavis ; then fperms 600 /var/log/FuzzyOcr.log fowners amavis:amavis /var/log/FuzzyOcr.log else fperms 660 /var/log/FuzzyOcr.log fowners root:fuzzyocr /var/log/FuzzyOcr.log fi fi * Install this unconditionally: dodir /etc/logrotate.d insopts -m0644 insinto /etc/logrotate.d newins "${FILESDIR}"/fuzzyocr.logrotate FuzzyOcr
Maintainers, can you please (re)consider to fix this bug? Or can QA team fix it?
Masked for removal
Package removed
