| Summary: | logwatch-6.0.1.ebuild (Update) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Meder Bakirov <bakirov> |
| Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | darren, rockoo |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
logwatch-6.0.1.ebuild
Logwatch Daily Cron file |
||
Created attachment 52348 [details]
logwatch-6.0.1.ebuild
Created attachment 52351 [details]
Logwatch Daily Cron file
This one goes into ${FILESDIR}.
I removed the next function from the ebuild:
pkg_postinst() {
einfo
einfo "you have to manually add ${PN} to cron..."
einfo "0 0 * * * /usr/sbin/logwatch.pl 2>&1 > /dev/null"
einfo
}
and added logwatch cron file instead - I think it's more convenient and
*nix-way :p
works for me. Is logwatch not being maintained in portage atm? The current stable version in the tree (4.3.2) is over 2 yrs old now :( using 6.0.1 on 5 x86 overhere for 4 weeks now - no probs - plz dump ping - works fine overhere for 2 months ... no, no one is really maintaining logwatch because no one cares about it 6.0.2 now in portage |
A new version bump for sys-apps/logwatch. 6.0 -> 6.0.1 (stable) A few small cleanup changes. Reproducible: Always Steps to Reproduce: 1. 2. 3. Also I removed the following function from the ebuild: pkg_postinst() { einfo einfo "you have to manually add ${PN} to cron..." einfo "0 0 * * * /usr/sbin/logwatch.pl 2>&1 > /dev/null" einfo } and added logwatch.cron file instead.