From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) by sourceware.org (Postfix) with ESMTP id 59FA93851C05 for ; Tue, 26 May 2020 03:32:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 59FA93851C05 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=yselkowitz@cygwin.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-498-49xPDIMuOWuau5TOwNkOGw-1; Mon, 25 May 2020 23:32:00 -0400 X-MC-Unique: 49xPDIMuOWuau5TOwNkOGw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B7A1F800688 for ; Tue, 26 May 2020 03:31:59 +0000 (UTC) Received: from ovpn-112-96.rdu2.redhat.com (ovpn-112-96.rdu2.redhat.com [10.10.112.96]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5917119D7E for ; Tue, 26 May 2020 03:31:59 +0000 (UTC) Message-ID: <9a00e8b06be5fc9f6f045c4a5df946333a9ec193.camel@cygwin.com> Subject: Re: [ITP] cairomm, as replacement for cairomm1.0 From: Yaakov Selkowitz To: cygwin-apps Date: Mon, 25 May 2020 23:31:57 -0400 In-Reply-To: References: User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_NUMSUBJECT, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2020 03:32:04 -0000 On Fri, 2020-05-15 at 11:30 -0400, Ken Brown via Cygwin-apps wrote: > cygport file attached. I've bumped the version to 1.12.2, which is the l= atest=20 > stable upstream release. Upstream has actually released 1.15.5, but the = News=20 > file says it's unstable and recommends that distros not package it. GNOME still uses the development/stable odd/even-minor versioning scheme (like the Linux kernel used to long ago). > I'm proposing an unversioned source package cairomm, as well as unversion= ed=20 > devel and doc packages. This is what we do with many library packages, a= nd it=20 > is consistent with Fedora's packaging. I would strongly recommend against this rename, and in fact it is Fedora that might have to adapt, because: > It will also ease future maintenance. I've looked at the upstream git re= po, and=20 > there's been an ABI change from 1.0 to 1.14 and then to 1.16. It would b= e=20 > annoying to have to create a new Cygwin package for each such change. 1.0 isn't an ABI version, it's an API version, and like many GNOME libraries, the GTKmm bindings carry the API version in all its directories and library names, so that multiple versions may be installed in parallel. (Any given application can use only one stack, but you can have some apps using the new and other apps using the current until they update.) Cairo is relatively newer than the rest of the stack, and so it hasn't been through this process before, but the others have. (That's they the current versions are e.g. 2.4 instead of 2.0, because the upcoming versions will be the third or even fourth API version for most of these packages; the previous versions were obsolete a LONG time ago. In fact, just remembering going through this last time, and then realizing how long ago that was, isn't making me feel any younger. :-) With the introduction of libsigc-3.0, this and the rest of the GTKmm stack is going to undergo a(nother) API version bump, with the new versions should be parallel installable with the current: Current: libsigc-2.0, glibmm-2.4, cairomm-1.0, atkmm-1.6, pangomm-1.4, gtkmm-2.4 and -3.0,=20 New: libsigc-3.0, glibmm-2.66, cairomm-1.16, atkmm-2.30, pangomm-2.44, gtkmm-4.0, etc. We're going to want to be able to have both for a period of time, and of course this could always happen again in the future. That's why they always been, and should remain, versioned. -- Yaakov