On Oct 19, 2007, at 20:16, Heikki Toivonen wrote:
For Windows and Mac (and Linux if users manually manage Chandler
install) we can make it work the way Reid suggested. For packaged
systems I think you would be required to scan the disk for
__repository__ directories. If you wanted to limit that to /home/
*/.chandler that would be a possibility, but users who placed their
repositories elsewhere would be pretty unhappy after an upgrade.
On Ubuntu, can't the app initiate an "apt-get update"? If so, it
could work the same way as the updates for Mac and Windows, except we
don't have to handle the downloading and updating.
All OS's have the potential for multiple users running Chandler, so
we should be scanning all of /home/*/.chandler, or wherever the
default location for user data is. We also need to prompt for the
ability to run as admin/root, otherwise the upgrade cannot(?) be
performed.
If we want to handle the command-line-savvy user, we can add text in
the upgrade dialog saying:
This automatic upgrade will automatically update all user libraries
in their default locations. If you or other users have run Chandler
in such a way as to create libraries elsewhere, you should back up
those libraries before performing this upgrade.
[ Upgrade ] [ Cancel ]
And maybe a blue underlined "click _here_ for details" could take
them to a wiki page where we explain that using the --repository flag
can be used to create/use libraries in any location.
[ I think we should avoid the word "repositories". "libraries" is
more user-centric. ]
Reid
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
