From owner-freebsd-ports@FreeBSD.ORG Sat Jul 13 01:18:40 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7581E1B5; Sat, 13 Jul 2013 01:18:40 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 3650D1AFC; Sat, 13 Jul 2013 01:18:40 +0000 (UTC) Received: by mail-oa0-f47.google.com with SMTP id m1so13842357oag.34 for ; Fri, 12 Jul 2013 18:18:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=m9NIt85TCVJIbMs7+sByC3Jelq9dbi80gy+gb/FhIiw=; b=m1D9/paNT+fi8A9USt1ADg/XBEwv4FKiKmVdvFpjIY54h8eP/AtMCA7Mx30qYT5X9k L1gCcy4udASUSvkuHxBDA0t8gjTeTgYdD6w3d7bnHy+lrz5OT6f+Ek+73DgCNi/ar/o4 UQQGRzxxZpJxkclivU0BoVL7mwcMV3IHqkn/1+5CL47GGrq1fbw32oF9j9n1k6ARrd3q Eu9vThwAuj5Tfn53/ryGr/O/lRTLHDtqQVN0RjfmMQ+J0zFBKeWlJ5SwJ2diLwLsIkLE TngyByRuhBg1GMXkFwMJUTaH7E3JZ7ySCkj9Z0uid+KKB8Y95dzgbLrVkHEv/1qP90Ci Ae/g== MIME-Version: 1.0 X-Received: by 10.182.101.169 with SMTP id fh9mr37270681obb.30.1373678319712; Fri, 12 Jul 2013 18:18:39 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.76.112.212 with HTTP; Fri, 12 Jul 2013 18:18:39 -0700 (PDT) In-Reply-To: <51E047A3.3060606@gmx.de> References: <51E047A3.3060606@gmx.de> Date: Fri, 12 Jul 2013 18:18:39 -0700 X-Google-Sender-Auth: CMncFPP-y-rHiTSotAu1bFttgPI Message-ID: Subject: Re: No UPDATING entry and some ports missed in curl update From: Kevin Oberman To: olli hauer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Sunpoet Hsieh , "ports@FreeBSD.org" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jul 2013 01:18:40 -0000 On Fri, Jul 12, 2013 at 11:14 AM, olli hauer wrote: > On 2013-07-12 19:47, Kevin Oberman wrote: > > It is a good thing to get curl up to date and I appreciate the effort > > involved by you and several others. > > > > While the curl port was updated to 7.31.0 and lots of ports using the > > sharable had bumps, I have found three ports on my system that link to > > libcurl and were not bumped: devel/git, textproc/rasqal, and > > textproc/redland. > > > > There was no entry in UPDATING, so there was no warning that saving a > copy > > of the old sharable would be a good thing, either. > > > > hm, > $ svn info ftp/curl| grep ^Last > Last Changed Author: sunpoet > Last Changed Rev: 322824 > Last Changed Date: 2013-07-12 11:02:43 +0200 (Fri, 12 Jul 2013) > > $> svn info /usr/ports/devel/git | grep ^Last > Last Changed Author: sunpoet > Last Changed Rev: 322833 > Last Changed Date: 2013-07-12 15:54:25 +0200 (Fri, 12 Jul 2013) > > $ svn log devel/git > ------------------------------------------------------------------------ > r322833 | sunpoet | 2013-07-12 15:54:25 +0200 (Fri, 12 Jul 2013) | 4 lines > - Bump PORTREVISION for ftp/curl shlib change > Notified by: Rotluchs (via IRC) > > So the latest git revision is OK > > > It seems the dependency list for textproc/rasqal textproc/redland is not > correct > > $ grep -R curl textproc/rasqal/ > $ grep -R curl textproc/redland* > (no output, so they fly under the bump radar) > > regarding your information this ports require LIB_DEPENDS+= curl... > > Maybe you can file a PR for this two ports. > > Yep. All tree were caught after I updated my tree in later commits. Looks like all of the ports relevant to my systems are now covered. I'd still like to see UPDATING have a note, though. Too many people will catch only some version bumps (as I did), so I think a heads-up is still appropriate for ports with this many dependencies. As to LIB_DEPENDS, both rasqal and redland depend on libraptor2.so. raptor2 depends on libcurl.so, so the dependency is inherited quite properly. It is simply neither practical nor appropriate to list every sub-dependency in every port's Makefile. Worst cases are things like gnome and kde4. Keepin g track of all of those manually would be a real pain in the neck and make maintaining such complex ports impractcal and that is why the ports system is designed to make this unnecessary. It gets even worse when, due to options, a port may or may not link to some sharable. Of course, this makes it impossible for quickly check for this sort of things when a sharable has a version bump an this is why I think bumping ports is simply inadequate.It is fairly trivial to check on ports on a given system that require a version bump, but testing thousands of ports for indirect dependencies does not do the trick. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com