On 2011-05-17, at 09:39 , Alexander Hansen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 5/17/11 9:30 AM, Charles Lepple wrote: >> On Sat, May 14, 2011 at 9:19 PM, Kevin Horton <khorto...@rogers.com> wrote: >>> I'm looking for advice on the best way to deal with a change in sylpheed >>> 3.1.1. Sylpheed is an X11 mail client. >>> >>> Up to now, user configuration data has been stored in ~/.sylpheed-2.0. >>> This has been changed to ~/Library/Application Support/Sylpheed in sylpheed >>> 3.1.1, but there are no provisions for existing users who upgrade from an >>> earlier version. If the user has not manually moved their configuration >>> data, sylpheed 3.1.1 acts as if it has never run before and prompts the >>> user to input their email settings. I wasted over two hours trying to >>> understand why sylpheed 3.1.1 did not use my existing configuration data >>> before I finally found out what was going on. I want to ensure that users >>> of this package don't suffer the same fate. >>> >>> I see the following options: >>> >>> 1. Create a post-install script that checks for the presence of >>> ~/.sylpheed-2.0. If this exists, and ~/Library/Application >>> Support/Sylpheed does not exist, it would copy the data in ~/.sylpheed-2.0 >>> to ~/Library/Application Support/Sylpheed. >> >> I'm not entirely sure we want a post-install script doing things on a >> per-user level - what happens if you have several users on the >> machine? If I am not mistaken, post-install runs as root, which means >> you have to be careful when copying permissions. > > Indeed, it does. > >> >>> 2. Same as above, but have fink explain the situation and ask the user to >>> confirm this is what he wants to do. This has the advantage of making the >>> user aware of this change. >>> >>> 3. User symlinks in ~/Library/Application Support/Sylpheed rather than copy >>> the data. Otherwise the same as option 1. >>> >>> 4. User symlinks in ~/Library/Application Support/Sylpheed rather than copy >>> the data. Otherwise the same as option 2. >>> >>> 5. Create a post-install script that tells the user about the change in >>> location for configuration data, and recommend that he move the data >>> himself before running sylpheed again. >>> >>> I'm leaving towards option 3. It has the advantage of allowing the >>> installation to complete without the need for user intervention. If the >>> user manually edits the data in ~/.sylpheed-2.0, thinking this is still the >>> default location, his edits are used due to the symlink in >>> ~/Library/Application Support/Sylpheed. >> >> What about putting that functionality in a wrapper script around the >> sylpheed binary? >> > > That seems like it would be handy from a user standpoint. > > If there's no ~/Library/Application Support/Sylpheed, check if there's a > ~/.sylpheed-2.0, and if so, tell the user that the data are being > migrated and perform the migration. Whether that would be symlink or a > copy would be up to Kevin. >
Thanks for the suggestions. I'm on the road for a few days, but I'll craft a wrapper script and post it for comments once things slow down. -- Kevin Horton Ottawa, Canada ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
