While merging media-tv/freevo-1.6.1, it overwrites the existing /etc/freevo/freevo.conf. This happens because of '"/usr/bin/freevo" setup ${myconf} || die "configure problem"' in the pkg_postinst function. IMHO the easiest solution is to skip the line if the file is already present, like if [ ! -e /etc/freevo/freevo.conf ] ; then "/usr/bin/freevo" setup ${myconf} || die "configure problem" else einfo "Skipping generation of /etc/freevo/freevo.conf" fi FF, Daniel
Are you sure that this is an issue? I always used to duplicate that file into /home/user/.freevo/ and then personalize it, as the file in home directory takes priority and that configuration can be personalized per-user. Also this is the suggested standard procedure for local_conf.py , new freevo documentation changed this behaviour?
(In reply to comment #1) > Are you sure that this is an issue? IMO, yes. From http://devmanual.gentoo.org/general-concepts/config-protect/index.html : "Packages must not attempt to override this system via pkg_postinst or similar." Sorry about RTFMing, but admins who configure for a multi-user system will be caught by this unexpectingly. FF, Daniel
Don't apologize, for sure something should be changed in the ebuild, but that manual page means only that the lines regarding /etc/freevo.conf should probably be placed inside src_install() instead than pkg_postinst(), while the solution you suggested would mean that /etc/freevo.conf would never be overwritten (that's bad!).
The new ebuild for 1.7.2 has fixed this -- freevo.conf is updated in the usual config-protect way, no explicit overwrites. (note, freevo is moving to sunrise as there is no official dev to maintain it)
I believe this is fixed in media-tv/freevo-1.7.2. Because <1.7 will not go stable, it won't be fixed there and the ebuilds removed soon. The "freevo setup" part is now executed in src_install since this is the only way I can think of to enable config protection. This sets up sane defaults based on the user's USE flags, but it could also break mplayer and other's PATH detection when using pre-built binpkgs. Please reopen with better ideas.
