On Sun, Sep 28, 2008 at 9:50 PM, Gary C Martin <[EMAIL PROTECTED]> wrote: > On 29 Sep 2008, at 02:06, Michael Stone wrote: > >> On Sun, Sep 28, 2008 at 03:21:49PM +0100, Gary C Martin wrote: >>> To Michael: Not sure who to direct this to, but should the post >>> install scripts do some extra checks for this potential upgrade >>> fluff? Not sure how many upgrades this could effect. >> >> What might we do with it if we found it? > > Well I can't think of a reasonable reason for leaving an old copy of > Journal kicking around in /home/olpc/Activities (faint chance a dev is
It's useful if you want to alt-boot back to an old build. > The Clac issue I guess is a special case in that that there was a > 'Calculate' from MIT that was replaced by Reinier's 'Calc' at some > point (at least as I understand the history), so I'm guessing > bundle_id didn't exist (or perhaps now depreciated service thingy) so > there's no way the updater would officially know to replace/remove > Calc and replace with Calculate. This could be a special case for post > cleanup, removing Calc if Calculate has been installed. In 9.1, I hope that Michael will provide me with the security framework I need to handle 'upgrades' between bundles with different IDs (and authors!), so I can express that 'calculate' is really an updated 'calc' and have that managed properly. So the 'fluff' ought to be removed at that time. > P.S. what's the post install script called by the way? I'm sure I've > seen it mentioned in passing or rushing past the console after an > install, doing 'rainbow' type stuff I think, hence me invoking your > name here. olpc-configure, part of the olpc-utils package. It's really a "first boot" script, but you "first boot" immediately "post install" so it wears both hats. --scott -- ( http://cscott.net/ ) _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel