continuous packaging? anyone?

[Harald Sitter]

On Mon, Aug 11, 2014 at 11:36 PM, Scott Kitterman <ubuntu at kitterman.com> wrote:
> On Monday, August 11, 2014 23:30:57 Harald Sitter wrote:
>> > - some of the packaging is really version centered (e.g. most games have a
>> > >= source:Version dep on kdegames-data which is from libkdegames) which
>> > would need fixing or packages will just be uninstallable - unless you
>> > build the whole full package set each day and only keep the date in the
>> > version. You might want to talk to debian about that or we'll just
>> > increase our diff.
>> Sounds like we are abusing version alignment TBH.
>
> No.  We're making the packaging system match upstream requirements.

That may well be, but we are still abusing a substvar because the
version *happen* to be the same because they are released at the same
time, they are not actually matching because they are of the same
source. It's really like if there was a manual dependency on an
externally built library and we used binaryVersion.

> There are similar issues elsewhere.  Even though KF5 is on a different release
> schedule than Plasma 5 and applications, there is no expectation that you can
> mix a random set of KF5 modules together and have them work.  They have to be
> from the same release.

I don't see how this is relevant to be honest. We'd CP all frameworks
so they would always be of the suitable compatible version. At any
rate a correct runtime and ABI dep tracking in the packaging would not
allow arbitrary mixing anyway.

HS