NetBSD Problem Report #49376

From www@NetBSD.org  Fri Nov  7 20:56:39 2014
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 70BE9A6674
	for <gnats-bugs@gnats.NetBSD.org>; Fri,  7 Nov 2014 20:56:39 +0000 (UTC)
Message-Id: <20141107205638.81C52A6688@mollari.NetBSD.org>
Date: Fri,  7 Nov 2014 20:56:38 +0000 (UTC)
From: jonthn+pkgsrc@pinacea.com
Reply-To: jonthn+pkgsrc@pinacea.com
To: gnats-bugs@NetBSD.org
Subject: Update libuv to v0.11.29
X-Send-Pr-Version: www-1.0

>Number:         49376
>Category:       pkg
>Synopsis:       Update libuv to v0.11.29
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    agc
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 07 21:00:00 +0000 2014
>Closed-Date:    Sun Dec 10 15:56:57 +0000 2017
>Last-Modified:  Sun Dec 10 15:56:57 +0000 2017
>Originator:     Jonathan Buschmann
>Release:        
>Organization:
>Environment:
>Description:
Attached you'll find a patch to update libuv to latest libuv with v0.1x API

I don't know how it's usually handled but libuv also has a newer API for the release 1.0 of libuv (currently rc2) which as far as I understood it is incompatible with 0.1x versions.


>How-To-Repeat:

>Fix:
https://gist.github.com/jonthn/231b49a85179b5775227

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: pkg-manager->agc
Responsible-Changed-By: bsiegert@NetBSD.org
Responsible-Changed-When: Thu, 27 Nov 2014 19:58:58 +0000
Responsible-Changed-Why:
Over to maintainer.


From: David Holland <dholland-pbugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/49376: Update libuv to v0.11.29
Date: Wed, 3 Dec 2014 16:26:55 +0000

 On Fri, Nov 07, 2014 at 09:00:00PM +0000, jonthn+pkgsrc@pinacea.com wrote:
  > >Synopsis:       Update libuv to v0.11.29
  >
  > Attached you'll find a patch to update libuv to latest libuv with v0.1x API
  > 
  > I don't know how it's usually handled but libuv also has a newer
  > API for the release 1.0 of libuv (currently rc2) which as far as I
  > understood it is incompatible with 0.1x versions.

 It depends on how many consumers of the old API they are and how hard
 they are to fix.

 If there aren't many and the changes are straightforward, it's
 probably better to patch them. If there are a lot, probably we'll move
 to having two packages (probably libuv0 and libuv1) so both are
 available.

 (For anyone reading this PR, note the existence of PR 49442 with
 patches for 1.x.)

 -- 
 David A. Holland
 dholland@netbsd.org

From: David Holland <dholland-pbugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/49376: Update libuv to v0.11.29
Date: Wed, 3 Dec 2014 16:36:36 +0000

 On Wed, Dec 03, 2014 at 04:30:08PM +0000, David Holland wrote:
  >   > I don't know how it's usually handled but libuv also has a newer
  >   > API for the release 1.0 of libuv (currently rc2) which as far as I
  >   > understood it is incompatible with 0.1x versions.
  >  
  >  It depends on how many consumers of the old API they are and how hard
  >  they are to fix.

 I see no consumers in pkgsrc at all, so I'm guessing it's probably
 better to just update it to 1.x. agc?

 -- 
 David A. Holland
 dholland@netbsd.org

State-Changed-From-To: open->closed
State-Changed-By: adam@NetBSD.org
State-Changed-When: Sun, 10 Dec 2017 15:56:57 +0000
State-Changed-Why:
Now we've got libuv-1.18.0.


>Unformatted:

Home	PR Database Search