[Debian-olpc-devel] Proper paths for sugar activities

Jonas Smedegaard dr at jones.dk
Sat Nov 22 16:12:39 UTC 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Nov 20, 2008 at 11:02:13PM +0400, Luke Faraone wrote:
>On Thu, Nov 20, 2008 at 11:28, Jonas Smedegaard <dr at jones.dk> wrote:
>
>> >On a slightly related note:
>> >
>> >The proper path, in my opinion, for sugar activities is 
>> >/usr/share/sugar/activities/, as this is what is used upstream, but 
>> >in debian/cdbs/1/class/python-sugar.mk a different path, 
>> >/usr/share/activities, is used. This has already been brought up to 
>> >your attention, and I was wondering how we should fix this: Shall we 
>> >simply correct the error in each git tree?
>>
>> Correct - this has been filed already as Debian Bug#485233 (see 
>> http://bugs.debian.org/485233 for more info).
>>
>> The local cdbs snippet python-sugar.mk needs to be updated for each 
>> activity. Done already for sugar-journal-activity.
>>
>
>I have since done this for all the other sugar-*-activities maintained 
>in git, although have not yet requested a upload.

Great! I'll have a look at it.

I am not sure what you mean by "have not yet reqested a upload" - I 
guess perhaps you wrongly assume some Ubuntu routine that does not apply 
for Debian: If/when you consider a package ready for Debian unstable, 
just say so here on the Alioth mailinglist, and someone in the team with 
upload rights (only me, currently) will double-check your changes, build 
and upload.


>On the subject of the journal activity: We'll need to remove it soon: 
>in the next version of sugar, for which tarballs are being released 
>today, (0.83.2) the journal has been merged into the main "sugar" 
>package.
>
>I assume the proper path is to remove sugar-journal-activity and set 
>sugar as {conflicts, replaces} it?

Yes, but wait a bit with that until we've decided on how to handle it:

a) multiple concurrent branches packaged

b) a single branch packaged - newest upstream for each package

c) a single branch packaged - newest upstream _stable_ release


I think a) is best, but it is also the most complex to maintain.

For now, I am sticking to the 0.82 branch.


  - 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)

iEYEARECAAYFAkkoL3cACgkQn7DbMsAkQLjlHwCfQlgUFuhcc6WlaYsFtoerv5w2
pJIAnRhy5xLqCgKAanxzj3nX2rYVDUKX
=cnwL
-----END PGP SIGNATURE-----



More information about the Debian-olpc-devel mailing list