On September 17, 2017 4:41:45 PM GMT+02:00, "Rainer Müller"
wrote:
>
>You are looking for the port -o option. You most likely want to delete
>the work/destroot directory first.
When destroot has previously succeeded, you also have to edit the statefile and
remove the
On 2017-09-17 16:41, Rainer Müller wrote:
> On 2017-09-17 16:35, Ken Cunningham wrote:
>> when working on the destrooting of complex ports it is tedious to have the
>> ports rebuild with each portfile edit, esp the big ports that need the
>> complex destrooting
>>
>> It must be possible to
thank you I don't think to check the man pages enough for macports issues.
I will go look there more often. -- Ken
> On Sep 17, 2017, at 7:41 AM, Rainer Müller wrote:
>
>> On 2017-09-17 16:35, Ken Cunningham wrote:
>> when working on the destrooting of complex ports it
On 2017-09-17 16:35, Ken Cunningham wrote:
> when working on the destrooting of complex ports it is tedious to have the
> ports rebuild with each portfile edit, esp the big ports that need the
> complex destrooting
>
> It must be possible to override this -- I feel I'm missing something
when working on the destrooting of complex ports it is tedious to have the
ports rebuild with each portfile edit, esp the big ports that need the complex
destrooting
It must be possible to override this -- I feel I'm missing something simple
somewhere. I hope this detail is not just buried
On 17 Sep 2017, at 00:15, Ryan Schmidt wrote:
> File ownership can be preserved on disk images, but that ownership is
> preserved by uid and gid, not by user name and group name.
I suspected this but didn't know how it actually works on OS X.
>> MP could also checked
On Sun, Sep 17, 2017 at 01:53:23PM +, Rainer Müller wrote:
On 2017-09-17 15:40, Umesh Singla wrote:
It's not a recent issue. I faced it 9 days ago as well. It keeps
restarting, aborting and then finally, got cancelled [0]. There are
absolutely no logs present.
I hardly think it's a Travis
On 2017-09-17 15:40, Umesh Singla wrote:
> It's not a recent issue. I faced it 9 days ago as well. It keeps
> restarting, aborting and then finally, got cancelled [0]. There are
> absolutely no logs present.
>
> I hardly think it's a Travis issue. It would have been fixed by them or
> informed if
this is still going on. some travis builds have been running almost 6 hours,
which would be great if they finally built something, but looks like it just
keeps resetting and starting over...
> On Sep 15, 2017, at 3:37 PM, Ken Cunningham
> wrote:
>
> Something