[Sugar-devel] [SoaS] Policy for activities for downstream inclusion
walter.bender at gmail.com
Tue Sep 14 10:09:17 EDT 2010
On Tue, Sep 14, 2010 at 10:05 AM, David Farning <dfarning at gmail.com> wrote:
> On Tue, Sep 14, 2010 at 5:27 AM, Simon Schampijer <simon at schampijer.de> wrote:
>> what is the current status for activity releases in order to include
>> them in distributions like Soas*? Do you guys need tarballs or did you
>> switch over to construct the rpms from the .xo? For example the latest
>> Paint rpm uses the .xo AFAIK (build even the binaries from the
>> non-python sources in the bundle).
>> And is the email from ASLO enough for packagers to know about new
>> releases? Any other notification that packagers need?
> In the .deb side of the universe, we prefer tarballs but we can work
> directly from the git repository.
Is it not still the practice to put tarballs on download.sl.o ???
> I have cced jonas for an official position.
>> * Of course any other downstreams that package/include activities are
>> happy to reply to this email too.
>> SoaS mailing list
>> SoaS at lists.sugarlabs.org
> SoaS mailing list
> SoaS at lists.sugarlabs.org
More information about the Sugar-devel