Lets stick to automating the current migration as close as possible. Are you using your blog to document your progress and challenges?
Email is not a great way to follow progress. Can you provide a daily summary of progress on open issue somewhere (blog) and email a link to the MP Dev list? Regards, Bradley Giesbrecht (pixilla) > On Jul 5, 2017, at 12:45 PM, Umesh Singla <[email protected]> wrote: > > Hi all > > Since there are things which need discussions on where to add what or what > checks, I guess we can keep them ongoing for now. I've moved to the migrate > action and we can finalize on the issues later when you're back? > > Thanks, > Umesh > > On Sun, Jun 25, 2017 at 10:27 AM, Joshua Root <[email protected]> wrote: > On 2017-6-25 08:24 , Umesh Singla wrote: > Anyway I tried consulting the existing migration guide. Why does it save the > list of all installed ports and then sets the requested flags? Only > installing the requested and let the dependencies figure out themselves - is > it an improvement we're making now? > > This works the way it does partly because of the "unrequested port with > requested variants" scenario I mentioned, and because users don't necessarily > have the requested flag set on all the ports they want. (We didn't always > have a requested flag. Also remember we can't currently distinguish between > requested and unrequested variants.) The idea with restore_ports.tcl was to > bring back the installed ports exactly as they were, as much as possible. > Active, inactive, requested and unrequested; all just as they were previously. > > - Josh >
