Yes, it could, but tracking down every copy of every activity is impractical for some deployments. Activities are shared around, on school servers, by e-mail, by USB drive. Adding a needless incompatibility breaks all this. May as well not have chosen .xo format in the first place if we're going to break it so badly.
And all for what? What possible justification have we to insist on this breakage? (A rhetorical question.) On Wed, Oct 30, 2013 at 07:31:03PM -0400, Tony Anderson wrote: > HI, > > I suspect a 10 line python script could update activity-info. > > It may be time to have two versions of each activity in ASLO. One > compatible > with 0.82 and the other with 0.100. > > Keeping in mind that 0.82 < 0.100. > > Tony > > > On 10/30/2013 05:04 PM, sugar-devel-requ...@lists.sugarlabs.org wrote: > >Message: 3 > >Date: Thu, 31 Oct 2013 08:03:58 +1100 > >From: James Cameron<qu...@laptop.org> > >To:sugar-devel@lists.sugarlabs.org > >Subject: Re: [Sugar-devel] service_name and bundle_id... again > >Message-ID:<20131030210358.gd20...@us.netrek.org> > >Content-Type: text/plain; charset=iso-8859-1 > > > >On Wed, Oct 30, 2013 at 12:27:57PM -0200, Gonzalo Odiard wrote: > >>>What you think about include it ?in Sugar?? > >Yes, include it. > > > >It has no effect unless it is necessary. (Small functional footprint). > > > >It fixes an unnecessary incompatibility. > > > >I have seen no significant evidence for excluding the change. > > > >If upstream is unwilling, then downstream may include it in packaging. > > > >-- James Cameron http://quozl.linux.org.au/ > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
