Re: Library packages: co-installability, build-depends, transitions
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matthew Johnson wrote:
> Separate -dev packages
> ----------------------
>
> The heavy-weight approach that is most like C and relies on the package
> manager a lot.
>
> + build-depends don't change between versions
By this you mean we build-depend on a virtual package like libfoo-dev, which
is Provided by libfoo0-dev, libfoo1-dev and so on?
This is not very good since it assumes the package will build correctly with
all future versions of the library. I prefer the more conservative policy of
build-depending on the actual dev package (also for C libraries).
> - lots of -dev packages which only contain 1 symlink
I think this is too much bloat to be acceptable.
> Post-inst symlink control
> -------------------------
Definitely much nicer.
> All the library packages contain postinst/prerm scripts which ennsure
> the symlink always points to the most recent version, there is no
> separate -dev.
If by "version" you mean "API version" (as you said above), then this is a
bad idea. That would mean that packages would suddenly build against a
different API version than intended.
So these symlinks should encode the API version in their name (similarly to
C), and point to the most recent upstream version that provides this API.
> - build-depends do change between versions
Yes, between API versions, as I think they should.
Cheers,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkp13VcACgkQXjXn6TzcAQm3WwCeKosrz5RUp8bQozYJFni0lH4Y
89UAoINvG6n11m5yK65VJy5zb2QQUF8g
=WYDt
-----END PGP SIGNATURE-----
Reply to: