On Wed, Oct 31, 2007 at 09:44:13AM -0700, Doug Barton wrote:
> On Wed, 31 Oct 2007, Peter Pentchev wrote:
>
>> On Wed, Oct 31, 2007 at 09:21:54AM -0700, Doug Barton wrote:
>>> On Wed, 31 Oct 2007, Peter Pentchev wrote:
>>>
Errr... maybe I should actually take a careful look at portmaster fir
On Wed, 31 Oct 2007, Peter Pentchev wrote:
On Wed, Oct 31, 2007 at 09:21:54AM -0700, Doug Barton wrote:
On Wed, 31 Oct 2007, Peter Pentchev wrote:
Errr... maybe I should actually take a careful look at portmaster first,
but after a cursory look at portmaster.sh.in... how do you handle the
cas
On Wed, Oct 31, 2007 at 09:21:54AM -0700, Doug Barton wrote:
> On Wed, 31 Oct 2007, Peter Pentchev wrote:
>
>> Errr... maybe I should actually take a careful look at portmaster first,
>> but after a cursory look at portmaster.sh.in... how do you handle the
>> case of a port installation that execu
On Tue, Oct 30, 2007 at 01:24:13PM -0700, Doug Barton wrote:
> I'm really stumped on this one, and I'm wondering if someone can come up
> with something clever here.
>
> In the last revision of portmaster I changed the order of how things are
> installed (parent port first, then any run-depends)
On Wed, 31 Oct 2007, Peter Pentchev wrote:
Errr... maybe I should actually take a careful look at portmaster first,
but after a cursory look at portmaster.sh.in... how do you handle the
case of a port installation that executes commands from a runtime
dependency? That is, a runtime dependency t
*sigh* Never mind. I found the problem. I missed a copy and paste of
one crucial line and didn't see it locally because of my .portmasterrc
file.
Doug
--
This .signature sanitized for your protection
___
freebsd-ports@freebsd.org mailing list
http
