[Debian-olpc-devel] Anyone working on packaging sugar-turtleart-activity
walter.bender at gmail.com
Mon Mar 30 14:18:18 UTC 2009
I am just back on line since meeting Petter in Bergen. I've love to
help get a bigger team helping with the Debian packaging and I am more
willing to be the guinea pig from the Sugar Activity developer
perspective. I will document the steps so that it is easier for the
A couple of comments re Turtle Art:
* I've only just begun work on making it run stand-alone from Sugar.
I'll continue to refine things over the next week or two. The only
version that will work at all right now is v46. I have pushed a few
additional patches since that release, but it is the last one that I
have packaged as an xo bundle and tar ball.
* Turtle Art Portfolio, which Ed referred to is an experimental
branch, but not worthwhile packaging. I pull from it into the mainline
Turtle Art, which has the portfolio features integrated.
I'll be back on line this evening when I will have a chance to review
the documents that Jonas has send.
On Mon, Mar 30, 2009 at 9:21 AM, Jonas Smedegaard <dr at jones.dk> wrote:
> On Mon, Mar 30, 2009 at 01:31:56PM +0200, Petter Reinholdtsen wrote:
>> [Jonas Smedegaard]
>>> Great that you work on this. And nice that you consider the Pippy
>>> packaging an improvement :-)
>> I picked Pippy at random, hoping it was a simple package with similar
>> needs. :)
> You were lucky then: Pippy is probably the best showcase of Sugar activity
> packaging - it is the one I recommend myself to people wanting to get their
> hands dirty on Sugar activity packaging :-)
>>> Would you be interested in maintaining Turtleart together with us at the
>>> OLPC Alioth team?
>> Yes, definitely.
>>> So far, the team consist of some 10 people but I have done most work so
>>> far. I am fan of CDBS and Git (as you might have noticed from that Pippy
>>> packaging) so you might consider doing similar for Turtleart.
>> I am not yet up to speed with git, but expect to be able to handle
>> that too, and do not have anything against CDBS, so I suspect that
>> should work just fine. Clues and tips on how to add a new package to
>> the alioth repository is most welcome.
> Attached is a couple of draft documents about packaging. One is the file
> currently included in packages like sugar-pippy-activity and the other is an
> early draft of what became the README.source that I posted earlier today.
> Both of them contain more details for newcomers to the packaging routines.
> Beware that one of the files describe way too much: Sugar activities do
> *not* use TopGit (I considered that, but learned that even if a very
> powerful tool it cannot handle multiple concurrent versions that I want -
> not for activities but for library packages (called "glucose" upstream)).
> To elaborate a bit on why I rewrote that file: I am not against documenting
> for newcomers. I just realized while working on it that trying to be both
> accurate and detailed ends in blurring both. A newcomer would probably need
> even more info than I provide anyway, and all those details gets in the way
> of getting a clear overview for experienced package maintainers.
> Hope those files is helpful, both concretely to kickstart your very welcome
> engagement in Sugar packaging, and also perhaps helpful for writing some
> wiki page or whatever for newcomers.
> Don't hesitate to ask about Git: I have become quite a fan of it, and
> learned a few small tricks on how to navigate.
> Here's one: The following command enable colored diffs, status messages,
> etc. when using a terminal (i.e. not when piped to a file or similar
> "colorblind" operations):
> git config --global color.ui auto
> Kind regards,
> - Jonas
> * Jonas Smedegaard - idealist og Internet-arkitekt
> * Tlf.: +45 40843136 Website: http://dr.jones.dk/
> [x] quote me freely [ ] ask before reusing [ ] keep private
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> -----END PGP SIGNATURE-----
More information about the Debian-olpc-devel