If one installs ntp fresh, then re-installs (emerge -1 ntp), /etc/ntp.conf will be removed. It will then be re-instantiated on the next emerge -1 ntp (and removed the next time, flip-floping back and forth). Here is, I believe, the culprit (exists in both ntp-4.2.4_p0 & ntp-4.2.4_p3): pkg_preinst() { if [[ -e ${ROOT}/etc/ntp.conf ]] ; then rm -f "${D}"/etc/ntp.conf fi }
Well, this breaks w/ FEATURES="unmerge-orphans" because the file becomes orphaned. Won't happen once it's been modified. Anyway, why's the pkg_postinst() there, no clue really.
Well, the pkg_postinst() just warns the user if the "notrust" option is used (it's just a caveat). It's the pkg_preinst() that is removing the file if unchanged, making re-installation have unpredictable/unexpected results. I'm not sure why it's done this way.
(In reply to comment #2) I meant preinst really, just a typo.