[GSoC] migration

[Umesh Singla]

Hi

On Sun, Jul 23, 2017 at 5:03 AM, db <iamsudo at gmail.com> wrote:

> On 22 Jul 2017, at 03:01, Umesh Singla <umeshksingla at macports.org> wrote:
> > I don't know, in the above example, what do you mean when you say "..you
> realize that from its deps..", like, realize how? I am just asking this if
> there's some other way to get info on the latest modifications that I might
> not be aware of.
> > 'sync' or 'upgrade outdated' provide the information what all ports got
> updated immediately on console but I'm not sure if it can be accessed later
> since the user may not realize that another port has broken immediately,
> like hstr here.
>
> Since MP doesn't keep logs (!) I keep them myself and investigate when
> something doesn't work properly.
>
> > Another thing that comes to my mind now is if, suppose, updated version
> of ncurses was actually required for some another port and reverting it to
> the older state could possibly result in breaking of that port.
>
> No, because, as I said, it would revert to a previous tree state. The
> thing is doing it by reinstalling only the upgraded ports and not the whole
> tree. It shouldn't be difficult to implement.


@Bradley, when we came up with re-installing all the ports, I had this
doubt too. It sure shouldn't be difficult, getting only the upper and lower
dependencies to check for, if a user is able to figure out the faulty port
himself.

I understand the part of migration but I'd like to know more about the
restore here. This conversation actually helped me focus on the
"install/activate the snapshot ports" part of your statement
"Restoring a snapshot would turn off all parts and install/activate the
snapshot ports with variants."
in one of your previous replies.

Can we help with such a use case here? To me, "it would revert to a
previous tree state" sounds like restore but with less complexity. Though
issues will come up even if the number of such ports is greater than 2 and
will make it hard for the user.

Regards,
Umesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20170727/69ba9110/attachment.html>