[Debian-olpc-devel] Bug#563436: Bug#563436: Bug#563436: sugar-0.88: sugar depends on python-numpy and python-pygames

[David Farning]

On Sun, Jan 3, 2010 at 1:40 PM, Jonas Smedegaard <dr at jones.dk> wrote:
> On Sat, Jan 02, 2010 at 09:04:09PM -0600, David Farning wrote:
>>
>>
>> On Sat, Jan 2, 2010 at 5:28 PM, Jonas Smedegaard <dr at jones.dk> wrote:
>>>
>>> On Sat, Jan 02, 2010 at 04:26:55PM -0600, dfarning wrote:
>
>> Ok, still learning the bug reporting system.  It seems pretty handy to:
>> Open a debian VM with quem  (when testing which debian version should I
>> use?) Update to latest packages.
>> Run tests
>> Report via reportbug.
>
> I guess you mean qemu (not quem).

My spell is horiable:)

> Develop packages using unstable.  Test using either unstable or testing
> (depending on what you want to test).
>
>
>>> Please file RFP (reguest for packaging) or ITP (intend to package) for
>>> each of those relevant-even-if-not-core activities.
>>
>> Distros don't need to worry about packaging the non-core activities.
>
> Yeah, there's many ways to get Free Software, only one of them being through
> Debian packages.
>
> It makes sense to support those wanting to use .xo bundles (honey-NN?) or
> build from source (sugar-dev-NN?), but only i not getting in the way of
> those wanting/expecting the main logic of Debian: Being fully installable
> while offline!
>
>
>>> sucrose-NN is intended to depend on all of core Sugar from Sugarlabs,
>>> recommend non-core parts shipped with Debian and suggest oddly packaged
>>> Sugar software (e.g. non-free packages).
>>
>> The problem is that because activity bundles (.xo) do not have the ability
>> to declare dependencies, activity developers must be able to depend on a
>> specific set package being available.  I don't belive that this list of
>> packages has been set in stone; Rather is is more of a convention that
>> activity developers can depend on python-numpy and python-pygames being
>> available.
>
> Yes, .xo bundles have their own pile of challenges. Those challenges are
> relevant only for those who want to mix Debian with that other oddity, so
> should be possible to avoid, and irrelevant to discuss in detail here IMO.

That sounds reasonable.  Wanting to install .XO bundles via
install_activity_bundle goes against the theory and practice of Debian
packaging.

One way we can get new packagers involved in Packaging Sugar on Debian
is to help package activities.  I'll try to file ITPs and start making
packages for the simple activities for Debain.  If someone downstream
wants to do something odd... It is on them.

>> Creating a separate honey package which contains these expected
>> dependencies makes sense... with the caveat that I _hate_ the terms;
>> glucose, sucrose, fructose, and honey.  I can never keep them straight.
>
> :-)
>
>
>
>  - Jonas
>
> --
> * Jonas Smedegaard - idealist & 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.10 (GNU/Linux)
>
> iQIcBAEBCgAGBQJLQPKyAAoJECx8MUbBoAEhRocP/1s6u3Lr3EzHfoRlSuUABzwJ
> m6YMcIzJpjxGkF5hXfYzBOsVkBXXiLpfgiHMsxnBkeWMBnV+eB+u31NcEJTH9Ynb
> qPLjsVqJeVct4V7jSHMQPCZQS7qqWTZdDrNbNHsOYfscyOU+XOkAeyVvD4jLDZf8
> pX5Npbqm6s++xJXrk8fFQsfqq61esnWTkMI35TpEDBWCOcKSx11fDp7o5ApL+DK0
> SZ43L+erNNTUTGrO3+Afcck17bc4xZ2w+k+BB5Fcg5FL+yzu6vS6N7O1UpwjwQGp
> qY+ZKeCtJBC4vQwZTx+U7/4qjPCRD5TzkCLejSKPdCJPHEjp7YnZ3dL+WTb2lhtO
> 4iT0ZY04Q8SvkSZkV9TOgF6HGnLvDxeo7Gy3MAqfd/bgrOcUqbzdy4KwM36I/lq2
> /Ql+4404TrLXZLIPkSVjiCG6pisZudx8yZTgYpIA3IxaaLrfeWY8xy/zdh1i8lsl
> 0EFldYwdd4tzzOiush9snowdqx2AQgo4gqKQkXIkayfWkkqWDkBbqpImfMxmnFuZ
> KRexbKslkc/deJLgbN6wUGoL+7EDi28YcBHj4SJw4H7XqbIgzc9GcYqHDYpoGCcB
> u3TfmrCUpDICkGf8ay+lGbNL0t30NydEWcWPx28NBHnR2/yIK+aX6dCPZRcFhQsu
> 6aCb7b4fn2S8Tb3oVbE6
> =O9Ed
> -----END PGP SIGNATURE-----
>
>