From owner-freebsd-ports@freebsd.org Wed Oct 12 05:20:54 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABDA0C0E094 for ; Wed, 12 Oct 2016 05:20:54 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9A825930 for ; Wed, 12 Oct 2016 05:20:54 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 99A9AC0E093; Wed, 12 Oct 2016 05:20:54 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 994A2C0E092 for ; Wed, 12 Oct 2016 05:20:54 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4810A92E; Wed, 12 Oct 2016 05:20:54 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from [IPv6:2600:1010:b002:9c94:ac14:b285:1f55:192f] (unknown [IPv6:2600:1010:b002:9c94:ac14:b285:1f55:192f]) by elvis.mu.org (Postfix) with ESMTPSA id 80152346DE24; Tue, 11 Oct 2016 22:20:48 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: harder and harder to avoid pkg From: Alfred Perlstein X-Mailer: iPhone Mail (14A456) In-Reply-To: <8b9c2ae9-03ad-0e4f-8abf-52147963e014@freebsd.org> Date: Tue, 11 Oct 2016 22:20:46 -0700 Cc: "ports@FreeBSD.org" , Baptiste Daroussin Content-Transfer-Encoding: quoted-printable Message-Id: <7B9295AA-F4F6-4E80-A35C-4C6C4C2493B2@freebsd.org> References: <638fe078-80db-2492-90be-f1280eb8d445@freebsd.org> <17b895a4-6ff3-9df5-91ac-6575df7fb206@freebsd.org> <8b9c2ae9-03ad-0e4f-8abf-52147963e014@freebsd.org> To: Julian Elischer X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2016 05:20:54 -0000 I feel like creative use of run/build-depends would work but I'm a bit tired= now. Well you probably don't want any or near zero deps down a library depe= nds path.=20 Sent from my iPhone > On Oct 11, 2016, at 10:08 PM, Julian Elischer wrote: >=20 >> On 11/10/2016 5:34 PM, Alfred Perlstein wrote: >> Make a slave port with an abbreviated pkg-plist bruh. ;) > yeeess, good idea, but that won't satisfy the dependency requirements of o= ther packages... you need to fool other packages, and that's the hard part. T= he way to do this is I think for pkg to have the ability to have two manifes= ts. >=20 > We are doing similar to what Roger says, but it's just so much work... >=20 >>=20 >> -Alfred >>=20 >>=20 >>> On 10/11/16 11:59 AM, Julian Elischer wrote: >>> As the number of dependencies between packages get ever higher, it becom= es more and more difficult to compile packages and the dependence on binary p= recompiled packages is increased. However binary packages are unsuitable for= some situations. We really need to follow the lead of some of the Linux gr= oups and have -runtime and -devel versions of packages, OR we what woudlbe s= marter, woudl be to have several "sub manifests" to allow unpacking in diffe= rent environments. >>>=20 >>>=20 >>> A simple example: libxml2 >>>=20 >>> This package installs include files and libraries and dicumentation etc.= >>>=20 >>> yet if I build an appliance , I want it to only install a singe file. >>>=20 >>> /usr/local/lib/libxml2.so.2 >>>=20 >>>=20 >>> The presence of this file will satisfy any runtime dependencies of packa= ges that require it. >>>=20 >>> Unfortunately there is no way to install just this file, and still repor= t that we have the package loaded, so >>>=20 >>> pkg will always try to reinstall it leading to a huge mess. >>>=20 >>> My current scheme is to unpack all packages into a larger staging area, a= nd *manually* (scripted) copy out only the files I need, and then copy the p= kg database, so that when run on the running appliance, pkg THINKS all the p= ackages are loaded on the appliance, even though only the runtime files are i= nstalled. This is what we in the industry call "a hack" :-) It is also not r= obust in the face of changing pkg versions. >>>=20 >>> It would be a lot better it pkg knew it was being asked to install only t= he runtime set, and coudl accurately store this information in its database= , allowing it to satisfy the needs of other packages that need that dependne= ncy only in a runtime manner. >>>=20 >>> Is any of this possible at the moment? >>>=20 >>> suggestions from the ports/pkg community are appreciated.. >>>=20 >>> Julian >>>=20 >>>=20 >>> _______________________________________________ >>> freebsd-ports@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"= >>>=20 >>=20 >>=20 >=20