From owner-freebsd-ports@FreeBSD.ORG Mon Mar 30 23:17:05 2015 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA79240E for ; Mon, 30 Mar 2015 23:17:05 +0000 (UTC) Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) (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 5E8D393A for ; Mon, 30 Mar 2015 23:17:05 +0000 (UTC) Received: by ykek76 with SMTP id k76so355092yke.0 for ; Mon, 30 Mar 2015 16:17:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=u3VPlgfVIiKlYR+/AxtbALJ9SXycavf7mmEkdxYsfic=; b=RwKmwAufBiilM5b1AbWd8ssMPMWdzfp3PvxsqPvmYh+qwaGITLpuOFgYAy/oxCZI4s nh4pxI9/XG77npJ69PxxQIZm9sch3Z+T/Q/7xIWHflv4PICQKrZqNMP1gJkQrjCybIxo JqJnsR9VliPT5E6Unqo236eDH8Cf5O6+4MqYQJYZ4gDT5xjyizfVmJlURRH9GNcR4prZ v6cM6tzK0d10MHfU4TdMXxKWj2TKB6Ntcrv+S8V/Xo0RDhyRSkCAjDoBCdoFTsehDPFA iFIOFaq9MZKlM+WA2DAp3qAjsBY+BEivPlTVQCjvH+EjFj+c+SpAYLTQhPKaivJ/aitI Sxew== X-Received: by 10.53.7.72 with SMTP id da8mr21098647vdd.58.1427757424472; Mon, 30 Mar 2015 16:17:04 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id cf6sm2073883vdc.15.2015.03.30.16.17.02 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2015 16:17:03 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 31 Mar 2015 01:16:59 +0200 From: Baptiste Daroussin To: ports@freebsd.org Subject: Re: Why pkg-install is run during port build? Message-ID: <20150330231659.GB30115@ivaldir.etoilebsd.net> References: <5519BE2F.50407@rawbw.com> <5519C520.6080004@rawbw.com> <44bnjaaydb.fsf@lowell-desk.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="98e8jtXdkpgskNou" Content-Disposition: inline In-Reply-To: <44bnjaaydb.fsf@lowell-desk.lan> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Yuri X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 23:17:05 -0000 --98e8jtXdkpgskNou Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 30, 2015 at 06:56:00PM -0400, Lowell Gilbert wrote: > Yuri writes: >=20 > > On 03/30/2015 14:42, Matthew Donovan wrote: > >> With FreeBSD packages and ports are the same. As it is tje same databa= se > > > > No, package and port are different things. > > Ports are the recipes to build packages or install directly, they are > > in file system under /usr/ports, and packages are the collection of > > binaries that can be installed, located in the repository, like one > > that is being pointed to by /etc/pkg/FreeBSD.conf > > > From your first message I wasn't sure you were actually running the > current ports/package tools (pkg(8)), but mentioning FreeBSD.conf tells > us that you are. >=20 > > My question is why pkg-install is run during the stage phase? Isn't > > this the wrong thing to do? I think only make install should run it. >=20 > The whole point of the stage phase is to install the port into a > transitional area (STAGEDIR), from which a package is built. That > package is what is actually installed into the real system. >=20 > This is the "new" way of doing things, meaning it's been around in > mainstream use for "only" a couple of years or so. And pkg-install is not run at all during stage if some ports are explicitly doing that they should be fixed! Best regards, Bapt --98e8jtXdkpgskNou Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUZ2WsACgkQ8kTtMUmk6Ew+KACgvuhkBMxWUOa4Uf/LJ3GPpglN TEUAni0oNjiAgZRXz3jNqErcpXa29YoW =2E3J -----END PGP SIGNATURE----- --98e8jtXdkpgskNou--