Re: SAGA 2.2.6
On 04/01/2016 11:58 PM, Johan Van de Wauw wrote:
> On Fri, Apr 1, 2016 at 11:45 PM, Sebastiaan Couwenberg
> <firstname.lastname@example.org> wrote:
>> Because the package will have to pass the NEW queue for saga-common, now
>> is a good time to split libsaga into separate packages matching the
>> SONAME (libsaga-api-2.2.6 & libsaga-gdi-2.2.6). Because the upstream
>> version is part of the package name then, you don't need to saga-depends
>> helper and virtual libsaga-2.2.6 package any more.
>> Do you want to split the library package or rather keep them bundled in
>> libsaga for now?
> I was planning to split them, because I don't really like the
> saga-depends helper.
It does mean that the library package names change for every new
upstream release, requiring the package to pass NEW and having the
upload sponsored. That may be a bit too much of an inconvenience.
> I've found a smallish license problem, reported upstream:
> Before uploading I'd like have an answer on that.
Good catch. I've subscribed to that issue too.
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
- SAGA 2.2.6
- From: Sebastiaan Couwenberg <email@example.com>
- Re: SAGA 2.2.6
- From: Johan Van de Wauw <firstname.lastname@example.org>