[maemo-developers] [maemo-developers] library updates

[From: Koen Kooi]

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

Adrian Neumaier schreef:
> I suppose you read this: http://www.debian.org/doc/maint-guide/ on how to 
> build proper debian archives.
> 
> But for that lib problem:
> it can't be too hard to write a control file like this:
> 
> <snip>
> Build-Depends: libfoo-dev ( >= 1.0.0-1), bar (>= 1.0.0)
> </snip>
> 
> This will pull libfoo in a package version >= 1.0.0-1 from the archive whilst 
> installing via apt-get install (i suppose this works with this graphical 
> installer too *g*) If libfoo 2.1.0 is in the archive this will still work. 
> 
> If the archive has two libs, same name, but different abi then the libs look 
> like this
> 
> libfoo1 (this has soname 1)
> libfoo2 (this has soname 2)
> 
> so in the end if your software needs libfoo1 you add to the build-depends 
> libfoo1-dev (>= ....)
> whilst software which uses libfoo2 has libfoo2-dev (>= ...) in the 
> build-depends.

Cute, but the real problem is something different:

Day 1:
Florian uploads gpe-calendar 0.99-12 + libeventdb1 0.36-17

Day 2:
Neal fixes bug in gpe-calendar, florian upload 0.99-13
Koen uses the AI, gets the updated calendar and rejoices

Day 3:
Neal fixes a bug in libeventdb1 without affecting API or ABI
florian uploads libeventdb1 0.36-18
Koen uses the AI and doesn't get the update, and is sad

Day 4:
Florian upload libeventdb1 with a Section: user/lib
Koen uses the AI, sees the update, and is happy

I hope this clears it up a bit :)

regards,

Koen








-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEwIU5MkyGM64RGpERApoJAJwPkkuuDKieaU86X5795RKkg1LfrACeLygR
0FOXdY33pjTtc+KZt0SRkJw=
=kJWy
-----END PGP SIGNATURE-----