On Sun, 24 May 2009 02:18:05 +0100
RW wrote:
>On Sat, 23 May 2009 20:22:03 -0400
>Robert Huff wrote:
>
>>
>> Marcin Rzepecki writes:
>>
>> > But why won't port do this automatically? Is there a way to force
>> > it before installing updated port version?
>>
>> Revuilding a dependency (
On Sat, 23 May 2009 20:22:03 -0400
Robert Huff wrote:
>
> Marcin Rzepecki writes:
>
> > But why won't port do this automatically? Is there a way to force
> > it before installing updated port version?
>
> Revuilding a dependency (here, dovecot) does not always
> require rebuilding the
Sat, May 23, 2009 at 08:22:03PM -0400, Robert Huff wrote:
> Revuilding a dependency (here, dovecot) does not always require
> rebuilding the dependant port. Sometimes, but not always.
Hello Robert,
first, thanks for the answer.
So, is there any dirty trick to make it happen? ;) For example
Marcin Rzepecki writes:
> But why won't port do this automatically? Is there a way to force
> it before installing updated port version?
Revuilding a dependency (here, dovecot) does not always require
rebuilding the dependant port. Sometimes, but not always.
Also: are you awar
Hello,
I have some questions about port dependencies. Let's take
for example following situation:
I have dovecot and dovecot-managesieve installed.
Today a new version of Dovecot showed up, so i'm upgrading it:
# make -C /usr/port/mail/dovecot
It builds ok, so i'm reinstalling port:
# make -C /usr
