From nobody Mon Feb 26 09:06:41 2024 X-Original-To: freebsd-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 4TjvrN3lBBz5Cknb for ; Mon, 26 Feb 2024 09:07:00 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:701:1000::435d]) (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 4TjvrN0tTNz4pgj for ; Mon, 26 Feb 2024 09:07:00 +0000 (UTC) (envelope-from trashcan@ellael.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (p200300fB4F137701f06F7d4484029d64.dip0.t-ipconnect.de [IPv6:2003:fb:4f13:7701:f06f:7d44:8402:9d64]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 4TjvrG4dJ3z1Rgf; Mon, 26 Feb 2024 10:06:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellael.org; s=dkim; t=1708938414; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Klv4xXfivuxCXOumPkw/fd/+o6PPGaSKpF4t94NReU0=; b=TOMRNd1YzedGuSthriorUy3vvL9ruTrEfIpdNs+kI1qoZCzjR9rngXGO13m/7RW5w2YfM8 Jsn7niFsqIdP2KSQyTKNEYJeJoYvLkpN/RpSVubJtHPcgmxG0E4k+XKUuqrv+UsZBcuxyN 5V42TVJUg8RblhNQE/oAOPN4FZC8gbo7lNLo+4lx51sQeBNVJJeEcFbxuIF11VM7rFIab+ M9fVo/LppuMEFZPflprGtQVGX8CBeeGnKMhXmHD5Wuasb1CiomXihCVnbLYwSneefDhv8Z J/5WB3JtpL+holtovnIutQ7Fcr/6kmqe7y1AsjVPP8oz/4WnI62VcVR/S+9odg== Content-Type: text/plain; charset=utf-8 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\)) Subject: Re: dns/knot3 and dns/knot-resolver do not get along with From: Michael Grimm In-Reply-To: <79302DD2-2673-4745-82B3-06BEEC907DAE@yahoo.com> Date: Mon, 26 Feb 2024 10:06:41 +0100 Cc: FreeBSD Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <6C622E06-4CFC-4296-B0C8-6279F6BD3FDB@ellael.org> References: <79302DD2-2673-4745-82B3-06BEEC907DAE.ref@yahoo.com> <79302DD2-2673-4745-82B3-06BEEC907DAE@yahoo.com> To: Mark Millard X-Mailer: Apple Mail (2.3774.400.31) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR] X-Rspamd-Queue-Id: 4TjvrN0tTNz4pgj Mark Millard wrote: > Michael Grimm wrote on > Date: Sun, 25 Feb 2024 19:46:22 UTC : >> I am trying to install dns/knot3 and dns/knot-resolver = simultaneously. >>=20 >> Compilation is achieved with the help of poudriere which complains = about dns/knot-resolver: >>=20 >> =3D=3D=3D> Installing existing package = /packages/All/knot-resolver-5.7.0_2.pkg >> [stable-default-job-02] Installing knot-resolver-5.7.0_2... >> [stable-default-job-02] `-- Installing knot3-lib-3.3.3_1... >> pkg-static: knot3-lib-3.3.3_1 conflicts with knot3-3.3.3_1 (installs = files into the same place). Problematic file: = /usr/local/include/knot/module.h >>=20 >> Failed to install the following 1 package(s): = /packages/All/knot-resolver-5.7.0_2.pkg >> *** Error code 1 >>=20 >> Stop. [=E2=80=A6] >> One needs to know, that there is a third port involved, namely = dns/knot3-lib, dependent for dns/knot-resolver. And, dns/knot3-lib is = simply a part of dns/knot3. >>=20 >> Thus, knot3-lib-3.3.3_1 as part of dns/knot3 shouldn't conflict with = dns/knot3. >>=20 >>=20 >> Questions: >>=20 >> #) Bug? >> #) How to resolve this conflict? >> #) Anyone running both ports in parallel? >=20 > If I understand right, if 2 more more installers should be allowed > to be used in the same context in overlapping it-is-installed > time frames, they must not conflict in what they install: no files > with the same paths. > Expected conflicts can be noted in the Makefiles to get earlier > notifications of the attempt to use conflicting material. But > having such conflicts means mutual exclusion as far as being > installed in overlapping time frames goes. > I'm not sure how your notes fit with the overlapping time frames > issue: is it valid to have knot3-?.?.? and knot3-lib-?.?.? > installed in overlapping time frames? FYI: I do not understand what you mean by 'overlapping time frames' Ok, there are 3 ports involved: 1) authoritative dns: dns/knot3 2) library part of dns/knot3: dns/knot3-lib 3) recursive dns: dns/knot-resolver 2) is needed by 3),=20 thus compiling 3) pulls all libraries and includes from 1), and stores them in the very same locations as 1) will. Thats, if I am not mistaken, the reason for pkg complaining 'pkg-static: = knot3-lib-3.3.3_1 conflicts with knot3-3.3.3_1 (installs files into the = same place).' Thus, IMHO, both ports dns/knot3 and dns/knot-resolver cannot be = installed simultaneously. One could install them in different jails, but = that is not an option for me. Possible solutions: 1) dns/knot3-lib should store its libraries and includes into a = different location as dns/knot3 does 2) discard dns/knot3-lib and make dns/knot3 and dns/knot-resolver = mutually dependent 3) =E2=80=A6? I am not an expert in ports internals, thus: what would the best way to = solve this issue? Thanks and regards, Michael