git migration, next steps

[Raphael Kubo da Costa]

Robby Workman <rworkman at slackware.com> writes:

> One of them has already (sorta) happened, though I don't recall the part
> involved.  Suppose several components depend on a particular library,
> e.g. libsomething, and the libsomething dev team releases a new version
> with some cool new feature and an API change.  Some of the components
> see that cool new feature and start depending on the new API, while
> others don't.  KDE SC -next includes some of each of those components.
> Now, which one should packagers ship?

Supposing component A which depends on libsomething 0.1 is in KDE module
`kdefoo' and component B which depends on libsomething 0.2 is in KDE
Module `kdebar', how would it be any different if A and B were released
as A-4.7.0.tar.bz2/B-4.7.0.tar.bz2 or kdefoo-4.7.0.tar.bz2 and
kdebar-4.7.0.tar.bz2?