From owner-freebsd-ruby@freebsd.org Mon Jul 9 12:28:05 2018 Return-Path: Delivered-To: freebsd-ruby@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F6AA10465B2 for ; Mon, 9 Jul 2018 12:28:05 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A3B959529D for ; Mon, 9 Jul 2018 12:28:04 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6656E10465AF; Mon, 9 Jul 2018 12:28:04 +0000 (UTC) Delivered-To: ruby@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41B4E10465AE for ; Mon, 9 Jul 2018 12:28:04 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D547F95297 for ; Mon, 9 Jul 2018 12:28:03 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mail-yw0-x235.google.com with SMTP id w76-v6so6455718ywg.4 for ; Mon, 09 Jul 2018 05:28:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamw-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9XcxYyU64oK/X1P96JtGeln0S9+aGWtuXmz/P1Qe8Z0=; b=134es1k/FU3A0h7Q6syylQd6FZ+6Lbg0BbgfOj+F0qdpzjcCsjhVJalgTT89v8IDCK 9gjY/nFE+44CNFWxT7A7a31h6iGOwnQ4+BHj1zPKqiyErnevIWCdaogxUBAmyV9BJLQL 6rOdR4K8yz3IvEVPU6vQnCZE24B12SeJ3n+TK7FFFu1SSCbSG4LgzlWfC1s2ZMMdgEod Kd0PsqXuIVdrMj23lyeuNLxSPSZhULyIWtc44xNFWmxn/FYQQw2J7Az/xhoTyXPqL7dr IpwoSKvq4/etCl2M6oYH0NZLty2jOVSyqBWB7hmOgiVS3cs6cfScvS6GFG/LM/Dh/afI rDFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9XcxYyU64oK/X1P96JtGeln0S9+aGWtuXmz/P1Qe8Z0=; b=rdobyTF/N9bvscVVsT+paYlJ0ewvytv3Axzzq4Ed8ygcJxDksWrCP7gYwlOQHjpmFJ q7lMsehJY5UPwml2N7zfuE8NIEvbxHeRNiTesJwDgPHV5gt/+S7rUqVbmUpMkKRORiD4 Sx/re/f2siX/JJDwJk/4PfxVzN0PtJ6KwZCA64HzLpqD+nwi2MWFcro+7maGS/kcyNK3 xbSUwfexk4MVYKFxe2HvUkvpauetKqWiMqGxvaL6xXdD70Gb/h3yTtSzu3V0VnZ9Fp0Y rK/c9cCu4OGsRsDh12LGXM4WT1qfsipY4yYaCfKX1LRgpCqzkfjeqeZlQ2W1GvBp1w04 zM3g== X-Gm-Message-State: APt69E1RJ3JuWUo8ukJaykMwPtkzHxp4S2dwCV5kFvMCiksf1z6gj1iN OKD+TU9k6OvAjvuS/ddolUHha5oNqkBZgbsSShipZg== X-Google-Smtp-Source: AAOMgpdBuzkGGOgWNmWcn7y06L1NaYmbsTkKc0AdWjIEVdU0CLmTndfoUKF/+OkG0FB16AnzC3Hfrkg7dB52lPgC67U= X-Received: by 2002:a0d:fd87:: with SMTP id n129-v6mr4071550ywf.439.1531139283074; Mon, 09 Jul 2018 05:28:03 -0700 (PDT) MIME-Version: 1.0 References: <6b43fe62-daac-a4f8-89a0-66cec1f6d933@utanet.at> <20180709030456.mvwdam3gzofvv45d@icepick.vmeta.jp> <731bb6c1-a673-2f9d-37c6-17cdc96c2214@freebsd.org> In-Reply-To: <731bb6c1-a673-2f9d-37c6-17cdc96c2214@freebsd.org> From: Adam Weinberger Date: Mon, 9 Jul 2018 06:27:47 -0600 Message-ID: Subject: Re: rubgem update to 3.2.7 To: se@freebsd.org Cc: meta@freebsd.org, w.schwarzenfeld@utanet.at, ruby@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 12:28:05 -0000 On Mon, Jul 9, 2018 at 1:13 AM Stefan Esser wrote: > > Am 09.07.18 um 05:04 schrieb Koichiro Iwao: > > On Mon, Jul 09, 2018 at 12:02:22AM +0200, Walter Schwarzenfeld via freebsd-ports wrote: > >> Portmaster tries to build the update in the wrong order. > >> > >> Right order for me was (depend on which packages are installed): > >> > >> rubygem-glib2 > >> rubygem-gobject-introspection > >> rubygem-gio2 > >> rubygem-gdk_pixbuf2 > >> rubygem-pango > >> rubygem-gdk3 > >> > >> rubygem-gtk3 > >> > >> rubygem-atk > > > > I can also confirm the issue. I always perform portmaster in order that > > you shown by hand when rubygem-gtk ports updated. portmaster needs to be fixed. > > A quick check shows that this is a problem with the port, which obviously > declares actual build dependencies as run dependencies. > > Please open a PR and let the ruby maintainers fix this issue. > > E.g. in x11-toolkits/rubygem-gtk3/Makefile: > > RUN_DEPENDS= rubygem-atk>=${PORTVERSION}:accessibility/rubygem-atk \ > rubygem-gdk3>=${PORTVERSION}:x11-toolkits/rubygem-gdk3 \ > rubygem-gdk_pixbuf2>=${PORTVERSION}:graphics/rubygem-gdk_pixbuf2 \ > rubygem-gio2>=${PORTVERSION}:devel/rubygem-gio2 \ > rubygem-glib2>=${PORTVERSION}:devel/rubygem-glib2 \ > > rubygem-gobject-introspection>=${PORTVERSION}:devel/rubygem-gobject-introspection > \ > rubygem-pango>=${PORTVERSION}:x11-toolkits/rubygem-pango > > Run dependencies are generally built after the port that needs them, since > they may themselves depend on resources provided by the respective port. That doesn't seem right. That is the reverse of a run dependency. If vim/Makefile: RUN_DEPENDS= ncurses then ncurses cannot possibly depend on vim as a BUILD_DEPENDS. poudriere builds RUN_DEPENDS in advance, and RUN_DEPENDS should be rebuilt in advance as well. > Build dependencies OTOH provide those files that need to be updated before > building a port. They may also be run dependencies (and often are), and in > that case they need to be in both the BUILD_DEPENDS and RUND_DEPENDS lists. This doesn't seem right either. Unless a ruby gem is compiling C or C++ modules, its dependencies are only needed at runtime. > I cannot modify the behavior of portmaster (i.e. build run dependencies > before the port that needs them, since this would break quite a number of > other ports with correct dependency specifications: Then portmaster would > try to build run dependencies before their prerequisites are available). > > So, I'm sorry, but portmaster will not be able to upgrade the rubygem ports > in the correct order, unless the port dependencies are fixed. I suspect this might actually be a portmaster issue. # Adam -- Adam Weinberger adamw@adamw.org https://www.adamw.org