Am 24.09.2008 um 14:10 schrieb C. Scott Ananian: > On Wed, Sep 24, 2008 at 4:33 PM, Bert Freudenberg <[EMAIL PROTECTED] > > wrote: >> how would I have to layout an activity update_url site if I want to >> provide >> a stable version for 8.2 but a later one for joyride builds? IIUC >> then the >> joyride updater will also try $update_url/8.2 just like a stable >> build does, >> right? Is there a way to do it without resorting to specific build >> numbers? > > One way is just to add the new version to > http://wiki.laptop.org/go/Activities/Joyride, which is only used by > joyride builds.
Does that override update_url? Or does the updater use the latest version found in either location? I'm unclear on the exact precedence of these repos. > But you raise a good point I started thinking about > this morning. One option is to move the /etc/olpc-release file to > point to 9.1 soon after 8.2 is released, so that you can put the new > versions at $update_url/9.1 -- would that work for you? Yes, I think it would. I wanted to put the latest version directly at update_url and the stable versions in a subdirectory named like the release: http://etoys.laptop.org/xo So if joyride moves to 9.1 and I do not provide a 9.1 dir it would pick up the default one. However - where would 8.2.1 development happen if not in joyride? - Bert - _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
