Re: migration instructions

[Rainer Müller]

On 2015-09-15 03:20, Ryan Schmidt wrote:
> 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 a dependency of something else on the
>> new platform only.
>>
>> 'sudo rm -rf /opt/local/var/macports/build/*' would do the trick but
>> apparently that wasn't "nice" 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 migration instructions now:
http://trac.macports.org/wiki/Migration?action=diff=87_version=86

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: migration instructions

[Rainer Müller]

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 (probably
>> just a few in most cases) which can be found by looking at
>> /opt/local/var/macports/builds and /optlocal/var/macports/logs I think,
>> saving a lot of time.
> 
> 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 a dependency of something else on the
> new platform only.
> 
> 'sudo rm -rf /opt/local/var/macports/build/*' would do the trick but
> apparently that wasn't "nice" enough.

For future versions, we could add that to the reclaim command, turning
this into something like 'sudo port reclaim --work'. Does that sound
reasonable?

At first I thought about an 'unclean' pseudo-port, but that would still
require parsing all the ports, which is the time consuming part here.
Also, removing everything is more accurate, as there could be work
directories that do not match any port in the ports tree anymore.

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: migration instructions

[Bradley Giesbrecht]

> 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 
> 
> 
> 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 to let it finish. Instead we should 
> clean just the ports that have incomplete builds (probably just a few in most 
> cases) which can be found by looking at /opt/local/var/macports/builds and 
> /optlocal/var/macports/logs I think, saving a lot of time.

Assuming default prefix would this [1] cover it?

> 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 would 
> be sufficient. Re-installing deactivated ports should probably not be done by 
> default since that is not returning you to the original state and there was 
> probably a reason (such as conflicts) why the ports were deactivated.

Untested, try this [2] to only install requested ports WITH variants. I’m not 
sure the last sed match works if there are variants name ".*_[0-9]".


[1] for port in $(find /opt/local/var/macports/{build,logs} -depth 2 -type d | 
awk -F/ '{print $NF}') ; do sudo port clean $port ; done
[2] port -q installed requested and active | sed -e 's,^ *,,' -e 's, 
(active),,' -e 's,@[^_]*_[0-9]*,,’



Regards,
Bradley Giesbrecht (pixilla)

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: migration instructions

[Joshua Root]

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 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 (probably
> just a few in most cases) which can be found by looking at
> /opt/local/var/macports/builds and /optlocal/var/macports/logs I think,
> saving a lot of time.

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 a dependency of something else on the
new platform only.

'sudo rm -rf /opt/local/var/macports/build/*' would do the trick but
apparently that wasn't "nice" enough.

> 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 would be sufficient. Re-installing deactivated ports should
> probably not be done by default since that is not returning you to the
> original state and there was probably a reason (such as conflicts) why
> the ports were deactivated.

This actually isn't a problem at all. We can't install old versions, so
what you end up with is the current version of each port, with the
previously active variants (if any) active, and any other listed variant
combinations inactive.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: migration instructions

[David Strubbe]

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 would be sufficient. Re-installing deactivated ports should
> > probably not be done by default since that is not returning you to the
> > original state and there was probably a reason (such as conflicts) why
> > the ports were deactivated.
>
> This actually isn't a problem at all. We can't install old versions, so
> what you end up with is the current version of each port, with the
> previously active variants (if any) active, and any other listed variant
> combinations inactive.
>

The multiple lines for a given port is just messy, but yes it is not really
a problem. And I guess I was mistaken about deactivated ports, the restore
script is checking that status.

David
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: migration instructions

[Ryan Schmidt]

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 a dependency of something else on the
> new platform only.
> 
> 'sudo rm -rf /opt/local/var/macports/build/*' would do the trick but
> apparently that wasn't "nice" 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?
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Migration instructions

[Jeremy Lavergne]

If there are missing dependencies, then the rebuild order may not be done 
correctly.

Trace mode or making a re-install list are the workarounds, as far as I know.

On Oct 17, 2014, at 13:56, James Berry jbe...@macports.org wrote:

 Given that the outdated pseudo port now returns all ports where the darwin 
 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 migration instructions here: 
 https://trac.macports.org/wiki/Migration should be updated?

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev