e" enough.
>
> Not nice enough for whom? It sounds good to me and would be quicker. It
> wouldn't delete work symlinks though... Would that be a problem?
Dangling work symlinks should not be a problem. They are only created
for use in port development.
I updated the migrati
On 2015-09-15 02:04, Joshua Root wrote:
> On 2015-9-15 06:10 , David Strubbe wrote:
>> 1. Running "sudo port clean all" takes a huge amount of time. Apparently
>> many hours for me; I didn't have the patience to let it finish. Instead
>> we should clean just the ports that have incomplete builds (p
On Sep 14, 2015, at 19:04, Joshua Root wrote:
>
> I've never liked this step much, especially since by definition you
> should only be building installed ports during migration. But it is
> theoretically possible that someone has a half-finished build for a port
> they don't have installed but is
On Mon, Sep 14, 2015 at 8:04 PM, Joshua Root wrote:
>
> > 2. The list of ports generated in myports.txt and requested.txt will
> > include ports that are deactivated, including one line for each version
> > of a port, whether active or not. One line total regardless of number of
> > versions woul
On 2015-9-15 06:10 , David Strubbe wrote:
> Hello all,
>
> I have just updated to Yosemite and used the migration instructions
> at http://trac.macports.org/wiki/Migration
>
> I want to point out two issues:
>
> 1. Running "sudo port clean all" takes a huge
> On Sep 14, 2015, at 1:10 PM, David Strubbe wrote:
>
> Hello all,
>
> I have just updated to Yosemite and used the migration instructions at
> http://trac.macports.org/wiki/Migration
> <http://trac.macports.org/wiki/Migration>
>
> I want to point out two i
Hello all,
I have just updated to Yosemite and used the migration instructions at
http://trac.macports.org/wiki/Migration
I want to point out two issues:
1. Running "sudo port clean all" takes a huge amount of time. Apparently
many hours for me; I didn't have the patience t
d
>
> This has worked well for me in the last few OS updates, including for
> Yosemite. If so, maybe the migration instructions
> here: https://trac.macports.org/wiki/Migration should be updated?
You could always do 'sudo port upgrade --force installed'. It didn't
always w
win
> version doesn’t match the current version, is it true that Migration of ports
> (following update of MacPorts) is as simple as:
>
> sudo port upgrade outdated
>
> This has worked well for me in the last few OS updates, including for
> Yosemite. If so, maybe the mig
, including for Yosemite.
If so, maybe the migration instructions here:
https://trac.macports.org/wiki/Migration
<https://trac.macports.org/wiki/Migration> should be updated?
James___
macports-dev mailing list
macports-dev@lists.macosforge.org
10 matches
Mail list logo
