From nobody Thu Jun 06 13:52:22 2024 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Vw5PS68pcz5MXC7 for ; Thu, 06 Jun 2024 13:52:44 +0000 (UTC) (envelope-from ps.ports@smyrak.com) Received: from ipv6.s149.cyber-folks.pl (ipv6.s149.cyber-folks.pl [IPv6:2a02:1778::113:254]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vw5PQ4G4qz42Zx for ; Thu, 6 Jun 2024 13:52:42 +0000 (UTC) (envelope-from ps.ports@smyrak.com) Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=smyrak.com header.s=x header.b=Sru4UdLX; dmarc=pass (policy=none) header.from=smyrak.com; spf=pass (mx1.freebsd.org: domain of ps.ports@smyrak.com designates 2a02:1778::113:254 as permitted sender) smtp.mailfrom=ps.ports@smyrak.com DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyrak.com; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=6Jnkh29QjgR+tX3OOo03k6yBJch8Le5qgfqaJkuUutw=; b=Sru4UdLXBS2YyILkOYqtm3q0pZ JLIyZjW2MmiRO6kEErEvFbi1D9DTps52QGIe4s2hrduudS5OQ5hkk6Zad9OasMTSgyl+qop1lk0LW 6DBqkAsHdnmEaIvfANJzJUiQdO6vu4BOiUn827jEPlq1RRM5+rZzdDtastvKSQTDowve7l5fmnuET BzfIbQwotvGqIwZPfprMPkoCHlNSG/gCYhpNeAboZDLaPxh4WnJTIf5Az+q2q7V07PZ2evabawIka INiQIpHfII45IOb1zww7biulRIX3pp0otd57oqCFk0AAK08TkDmMUY/iBn8l1ZR5Ens+E234pRB83 +zrh8eLQ==; Received: from 93-181-165-201.internetia.net.pl ([93.181.165.201] helo=daleth.home) by s149.cyber-folks.pl with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1sFDXl-0000000BBB6-1e38; Thu, 06 Jun 2024 15:52:41 +0200 Date: Thu, 6 Jun 2024 15:52:22 +0200 From: Piotr Smyrak To: ports@freebsd.org Cc: martin@waschbuesch.de Subject: Re: dependency hell Message-ID: <20240606155222.28742590@daleth.home> In-Reply-To: <9c709d96-98b9-490a-baab-8a076ef4fd7e@quip.cz> References: <31f85810-cb4d-46b8-8fb9-4923f6499a31@waschbuesch.de> <9c709d96-98b9-490a-baab-8a076ef4fd7e@quip.cz> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Id: piero@smyrak.com X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.63 / 15.00]; NEURAL_HAM_SHORT(-0.99)[-0.994]; NEURAL_HAM_MEDIUM(-0.97)[-0.975]; NEURAL_HAM_LONG(-0.96)[-0.964]; DMARC_POLICY_ALLOW(-0.50)[smyrak.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a02:1778::113:0/116]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; ASN(0.00)[asn:41079, ipnet:2a02:1778::/48, country:PL]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; R_DKIM_PERMFAIL(0.00)[smyrak.com:s=x]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[ports@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[smyrak.com:~] X-Rspamd-Queue-Id: 4Vw5PQ4G4qz42Zx On Thu, 6 Jun 2024 15:16:33 +0200 Miroslav Lachman <000.fbsd@quip.cz> wrote: > On 06/06/2024 14:30, Martin Waschb=C3=BCsch wrote: > > Hello port list, > >=20 > > I use poudriere to create my own repositories for typical > > webservers we run (apache, mariadb, php). > >=20 > > Some change(s) in some port(s) seem to have introduced loads of=20 > > additional dependencies (X, wayland, gtk) mostly unwanted on the > > type of system we run. > >=20 > > I know how to find out dependencies for installed packages, but > > that does not help here as the packages are not yet built. > >=20 > > Is there a way (other than searching the commit logs for all > > packages I plan to build) to pinpoint the package(s) that > > introduced the new dependency? =20 If you have the ports tree extracted and updated, running: $ cd /usr/ports/`pkg info -qo foo` $ make all-depends-list =E2=80=A6 in the package port dir and its direct dependencies shall let you figure it out. Please do note that dependencies may change depending on the choice of OPTIONS. Packages are built with the defaults chosen by port maintainers.=20 If your ports tree is indeed a git repo with something like this you shall get a sinking list of changes made to Makefiles of your affected port/package dependencies: $ cd /usr/ports/`pkg info -qo foo` $ make all-depends-list | sed -e 's@/usr/ports@../..@; s@$@/Makefile@;' | xargs git log -p --=20 Piotr Smyrak