[IAEP] IAEP Digest, Vol 14, Issue 58

[David Van Assche]

Though my usage case of packaging a lot of honey is not totally common, even
without that, I am still responsible for a good 50-100 packages that make up
sugar and its dependencies... if we have access to the source in a common
way (like git) it means I can script some bash stuff to do a lot of
processing automatically on a monthly basis. For every exception it takes me
2 times longer than it normally would, so I would love to see everything in
the git repos at least. A bz2 is nice, but that can be scripted. The
problem, and this is true of sugar, is that not all source is the same nor
can it be packaged in the same way. Take the sugar-colors activity, for
example. To package that, we need the prebuilt binaries that the Makefile
would otherwise take care of installing... So we need the source, the
binaries that are generated, and any dependencies required to generate those
binaries... Then we need to tell the rpm where to install all this.

kind Regards,
David (nubae) Van Assche

On Fri, May 29, 2009 at 10:48 AM, Tomeu Vizoso <tomeu at sugarlabs.org> wrote:

> On Thu, May 28, 2009 at 23:21, Gary C Martin <gary at garycmartin.com> wrote:
> > On 28 May 2009, at 18:04, James Simmons wrote:
> >
> >> David,
> >>
> >> I thought I had answered that one with a previous email.  First, you
> >> can see the latest git changes at this link:
> >>
> >>
> http://git.sugarlabs.org/projects/readetexts/repos/mainline/trees/master
> >>
> >> I don't know why the main page doesn't show that.  It never has;
> >> it's something I've just lived with.
> >>
> >> Second, the activity is 100% python, so if you have the .xo file you
> >> have all the source there is.
> >
> > Yes, my feelings exactly...
> >
> >> I understand there is an option in python setup.py that lets you
> >> create a source package but I've never used it.  If I created such a
> >> package where would I post it?
> >
> > Unfortunately what David is referring to (and I don't mean to pick on
> > David) is the desire of packagers to have everything provided as .bz2
> > for individual bundling. Now I don't understand the desire, or need
> > for this, and have yet to see a good argument for it, but it does seem
> > (for now at least) that if an Activity author wants to make life
> > easier for a packager to distribute their Activity, they should:
> >
> > 1) Use ./setup.py dist_source (this generates a .tar.bz2 file in ./dist)
> >
> > 2) Scp the .bz2 file to shell.sugarlabs.org/upload/sugar/sources/honey/
> > <activity-name>/... This makes it appear at
> http://download.sugarlabs.org/sources/honey/
> >  but you will need to request shell access first by creating a trac
> > ticket at dev.sugarlabs.org (I'm happy to upload the .bz2 bundle for
> > you if you email it to me, as it may take a while to get an account,
> > and making every Activity author use a shell account on sunjammer is
> > not very scalable).
> >
> > 3) Edit the Honey table at
> http://wiki.sugarlabs.org/go/Development_Team/Source_Code
> >  and make sure it lists and points to the latest .bz2
> >
> > 4) Edit another wiki table at
> http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap
> >  if you want to get Read Etext onto the SoaS distro.
> >
> > 5) Write a Subject: [RELEASE] <activity-name>-<version> email and send
> > it to sugar-devel providing a link to the .xo bundle, a link to
> > the .bz2, and some release notes about what's new, so that distro
> > maintainers and packagers know it available for packaging.
> >
> > Quite a few additional hoops there for authors to jump through, sorry,
> > and you'll need to repeat this for each subsequent release.
> >
> > Suggestions for improving this workflow anyone? And I'd love to
> > understand what is so good about .bz2 and/or if they really are needed
> > why a packager can't generate them with ./setup.py dist_source.
>
> As you said, this is only required if the activity author wants its
> activity packaged in a distro, which I personally think should not be
> a very common case.
>
> Regarding why packagers request that the source is well advertised and
> its file name and format follows a common scheme my understanding is
> that it's because it makes their life easier. Take into account that
> many packagers are responsible for several packages (not all of them
> related to Sugar) and if each of them has a completely different
> process, the amount of work to do grows quite fast.
>
> I would like that Sugar Labs regards distro packagers as partners that
> fulfil a crucial role in the process to deliver Sugar to children. As
> such, we should respect their knowledge about their tasks and see how
> best we can work together.
>
> Regards,
>
> Tomeu
>
> > Regards,
> > --Gary
> >
> >> James Simmons
> >>
> >>
> >> David Van Assche wrote:
> >>>
> >>> Please could you also give us the link to the source for the
> >>> readetexts activity. We have it packaged in openSUSE, and I'd like
> >>> to be able to offer the latest version...
> >>>
> >>> kind Regards,
> >>> David Van Assche
> >>>
> >>> P.S. The last git commit I see for read e texts was in March...
> >>>
> >>> On Thu, May 28, 2009 at 5:26 PM, James Simmons <
> jim.simmons at walgreens.com
> >>> > wrote:
> >>> Tomeu,
> >>>
> >>> This link is not to the main Gutenberg site, but to a Czech Republic
> >>> site.  The books seem to be all in Czech.  Project Gutenberg does not
> >>> list this site as an affiliate.  I don't know what's going on here.
> >>>
> >>> James Simmons
> >>>
> >>>
> >>> Tomeu Vizoso wrote:
> >>> > Hmm, actually I looked for this book and couldn't find it from
> >>> inside ETexts:
> >>> >
> >>> > http://www.gutenberg.cz/kniha.php?etext_nr=357
> >>> >
> >>> > Any idea why?
> >>> >
> >>> > Thanks,
> >>> >
> >>> > Tomeu
> >>> >
> >>>
> >>>
> >>> _______________________________________________
> >>> IAEP -- It's An Education Project (not a laptop project!)
> >>> IAEP at lists.sugarlabs.org
> >>> http://lists.sugarlabs.org/listinfo/iaep
> >>>
> >>
> >> _______________________________________________
> >> IAEP -- It's An Education Project (not a laptop project!)
> >> IAEP at lists.sugarlabs.org
> >> http://lists.sugarlabs.org/listinfo/iaep
> >
> > _______________________________________________
> > IAEP -- It's An Education Project (not a laptop project!)
> > IAEP at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/iaep
> >
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/iaep/attachments/20090529/ae232796/attachment.htm