Hi. I need some help before I upgrade smplayer in F9. The new version changed it's config dir from ~/.smplayer to ~/.config/smplayer. [1] The user has to move his old custom config manually if he wants to preserve it. Although smplayer would start normally, the custom config of the user wouldn't be used. So I'm not sure how I introduce this update in F9. We don't have such thinks like bodhi and it's upgrade notifications. So what would be the best way to inform the users that they have to manually move their config files to preserve them? Blog it on the new rpmfusion blog? :)

On Sat, 15 Nov 2008 02:09:58 +0200, manuel wolfshant wrote: > On 11/15/2008 01:54 AM, Sebastian Vahl wrote: > > Hi. > > > > I need some help before I upgrade smplayer in F9. The new version > > changed it's config dir from ~/.smplayer to ~/.config/smplayer. > > [1] The user has to move his old custom config manually if he > > wants to preserve it. Although smplayer would start normally, the > > custom config of the user wouldn't be used. > > > > So I'm not sure how I introduce this update in F9. We don't have > > such thinks like bodhi and it's upgrade notifications. So what > > would be the best way to inform the users that they have to > > manually move their config files to preserve them? Blog it on the > > new rpmfusion blog? :) > > > > > Any particular reason to not do a cp ~/.smplayer ~/.config/smplayer > (or even a ln -s) in %post ? Yes. In %post, ~ doesn't expand to every user's home directory. Instead, you probably want to patch the source code to rename/copy/move the config dir/file if ~/.config/smplayer doesn't exist already.