From owner-freebsd-ports@FreeBSD.ORG Thu Oct 3 07:56:47 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3F21B4F7 for ; Thu, 3 Oct 2013 07:56:47 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog106.obsmtp.com (eu1sys200aog106.obsmtp.com [207.126.144.121]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 966F92ADE for ; Thu, 3 Oct 2013 07:56:46 +0000 (UTC) Received: from mail-we0-f173.google.com ([74.125.82.173]) (using TLSv1) by eu1sys200aob106.postini.com ([207.126.147.11]) with SMTP ID DSNKUk0jHjMD0edSR7u7J4MvSTI8R/CrV0e5@postini.com; Thu, 03 Oct 2013 07:56:46 UTC Received: by mail-we0-f173.google.com with SMTP id u57so1168186wes.32 for ; Thu, 03 Oct 2013 00:56:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:message-id:to:subject:cc :reply-to:in-reply-to; bh=rrs10RTM6HSLQz2fi1hW50d2IQXHTD2xPMP/gr5khAY=; b=TXSqs4nWnYGl4jl16x5+N62qRIdkBqlf+Jtr0DYUw7SkTBnLt2nInj7F5BarSwCdU5 8lpjEpObrCzfVISm3ALmGFg3Zfz2Wjmh2C7rNg+wYlLj4uvrLAPgveYcMAXgrqc2fyrq /2eURlPHBIqypglc1NwGNhNAzJYmeC8dOWAuqXo3SNyp/GeNkIWwz8almhds4M+i/R8q LT89gIsDFRRD67uBSBqqfDnuGjN52LLiQi8ZpWetg3m+2CQAabY7Cj5yXxC7q/Ce2qdo e/Rx8QXPMb3iC21qiC/f1RA7P8G8kR3xX3SsLrLCPICvgo7NPu37ysgiJrIIREHnnq5w a2cg== X-Gm-Message-State: ALoCoQkpEl9+4pjDR3JAcdxt7SZs0pFA76ZkyHZFm/ozW/F01nRu4pp9mFFRzq12stPZhDaEvxsyBoN9FC/EHA2hRyjIxDugR0siMEXMrCuEfiqoQF/G0L71MzFiwMdnBk0MX10BMDW3yuSoT7Nq9fg2tU58XeyvjFelWce4SKzFJ+kTpP73xt4= X-Received: by 10.194.23.73 with SMTP id k9mr6161360wjf.24.1380786974720; Thu, 03 Oct 2013 00:56:14 -0700 (PDT) X-Received: by 10.194.23.73 with SMTP id k9mr6161356wjf.24.1380786974632; Thu, 03 Oct 2013 00:56:14 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id i8sm11187982wiy.6.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Oct 2013 00:56:13 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r937uBpR092100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 3 Oct 2013 08:56:12 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r937uBcj092099; Thu, 3 Oct 2013 08:56:11 +0100 (BST) (envelope-from mexas) Date: Thu, 3 Oct 2013 08:56:11 +0100 (BST) From: Anton Shterenlikht Message-Id: <201310030756.r937uBcj092099@mech-cluster241.men.bris.ac.uk> To: bapt@FreeBSD.org, stephen@missouri.edu Subject: Re: Explain staging In-Reply-To: <20131003061511.GF85314@ithaqua.etoilebsd.net> Cc: freebsd-ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bris.ac.uk List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 07:56:47 -0000 >Date: Thu, 3 Oct 2013 08:15:11 +0200 >From: Baptiste Daroussin >To: Stephen Montgomery-Smith >Subject: Re: Explain staging > >On Wed, Oct 02, 2013 at 10:44:32PM -0500, Stephen Montgomery-Smith wrote: >> I have not been following discussions recently. There is this new thing >> called staging. I don't seem able to find the original emails where >> this was introduced. >>=20 >> Is there an email or a website which explains in some detail how staging >> works? It is badly messing with a port I am developing. I can fix it >> by setting NO_STAGE=3Dyes, but I would like to get a better idea of why it >> is failing. The failure is during the build process. >>=20 >> Sorry for not following closer. > >Not a problem. > >Staging is basically installing everything into a staging area "${WRKSRC}/s= >tage" >before messing up the system. What most of package system calls DESTDIR or >FAKEDIR. sorry, I still don't get it. What is achived by staging? > >=46rom that stage a create can be directly created (even as a single user).= > or the >stage can be sync into the filesystem. I don't understand what you mean. Do you mean that an unprivileged user can somehow install software from ports not under /usr/local? > >2 new targets can help you staging your ports: make check-orphans and make >makeplist. > >You should have received 2 mails from me with some details about staging: >one called "[HEADSUP] Stage support for the ports tree" >and on called "Staging, packages and more" (very recent as of yesterday) > >The following wiki page https://wiki.freebsd.org/ports/StageDir has been cr= >eated >for tips and helps around staging. I've read your mails and the wiki page, but still not sure what, if anything, I need/could do with my ports. I trust you know what you are doing, but the meaning is not clear to me (yet). Is the idea that all ports must/should support staging? If a port doesn't support staging, will it fail portlint checks? Thanks Anton