Explain staging

[Stephen Montgomery-Smith]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/03/2013 07:44 AM, Stephen Montgomery-Smith wrote:
> On 10/03/2013 07:32 AM, Baptiste Daroussin wrote:
>> On Thu, Oct 03, 2013 at 07:22:35AM -0500, Stephen
>> Montgomery-Smith wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>> 
>>> On 10/03/2013 04:54 AM, Baptiste Daroussin wrote:
>>>> On Thu, Oct 03, 2013 at 10:58:56AM +0200, Alex Dupre wrote:
>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>> 
>>>>> Baptiste Daroussin ha scritto:
>>>>>> Here you are: 
>>>>>> http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html
>>>>>
>>>>>
>>>>>>
>>>
>>>>>>
>
>>>>>> 
I
>>>>>> 
>>>>> was referring the the previous one: "[HEADSUP] Stage
>>>>> support for the ports tree". Dunno if it had additional
>>>>> info or this second one is enough.
>>>>> 
>>>> I mixed both in one :)
>>> 
>>> I do appreciate the explanations very much.
>>> 
>>> I am having a problem with a port in which if NO_STAGE is not 
>>> set, then the build part of the process fails.  As far as I
>>> can tell, staging should not effect the build part of the
>>> process in any way. So two questions: 1.  If I set NO_STAGE=yes
>>> in that port, is this going to be a big problem?  It will have
>>> to be a work around until I can get the next question answered:
>>> 2.  Any ideas on why staging would effect the build process?
>>> The port includes subpackages that use "./configure; make; make
>>> install" and are supposed to install into $WRKSRC/local, but
>>> instead sometimes installs into 
>>> $WRKDIR/stage/portname/work/pkgname/local.
>>> 
>>> Thanks, Stephen
> 
>> Which port is that? Maybe I can help?
> 
> It is math/sage.  But I think it is working in this current port.
> The problem, I think, is in math/sage-devel, which exists only in
> my private ports tree.

Also, I am not in a super hurry to fix this problem.  Work and family
life are quite big stressors in my life right now.  Fixing easy bugs
and updates to the ports is quite relaxing, but something that will
require a full investigation like this is going to be on a waiting list.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSTWk5AAoJEC3xK9GaktgHoT0IAJN0Sn6rBCBetZqa2FuM/EPm
GNe4diIX/cs0UKYZZQN9Gj8g5EXNgNaDJ1nPuTHt4jAyo92YYM6GTLSsPBhfY7rA
D6cfmYMUEVY2YtKODigjMb7XF6F9Lv6hZkNnuiZGUwAmW0FmDCejysP0M+qlmHEf
xgLLhzCJ1w64vbgr7/OzMdb4FftR/ja1F5UFJjwGZakVcSQEhRL0N4kdEzTC0/PT
My85TEvyUg0N1QrcZRrvLfcZFkpSeqjPscRo+LptvVSFf2PtkTZOOtArYbFIattY
+oCn/G301YLawG78lRrnLYxuCxYVHwzZSalMTzcc5c61Hdvf2ooCUBokI5MoAfc=
=qgOF
-----END PGP SIGNATURE-----