On 2017-7-21 08:22 , Umesh Singla wrote:
> When we install, is it fine to use [mportexec $workername
$install_target] from migrate.tcl?
I’m sorry, I don’t know base well enough to answer this. Can you
please ask Clemens or Josh?
@Clemens @Josh, can you clarify this?
If that's ru
On 2017-7-22 11:01 , Umesh Singla wrote:
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. May
be, we could get all the ports which de
Hi
On Fri, Jul 21, 2017 at 5:39 PM, db wrote:
> On 21 Jul 2017, at 13:02, Umesh Singla wrote:
> > Unless we have a snapshot of the previous state, that is, before it got
> hampered.
> > But then again, we reinstall all the ports presently. At this time, it
> could be hard for me to detect what
Forwarding this to macports-dev.
-- Forwarded message --
From: Umesh Singla
Date: Fri, Jul 21, 2017 at 4:32 PM
Subject: Re: [GSoC] migration
To: db
Hi
> > Snapshot and restore should be able to be executed without migrate.
>
> I have a question and I haven't been following in
On Jul 21, 2017, at 12:56, Kenneth F. Cunningham wrote:
> If it works like I think it does, PortGroup muniversal does manually what
> Apple's driverdriver.c does behind the scenes for apple gcc compilers
> (gcc4.2, etc) and is built in to clang … so PortGroup muniversal should not
> be needed
On 2017-07-21, at 4:21 AM, Ryan Schmidt wrote:
> "variant universal {}" declares that a universal variant should be offered to
> the user, and that it requires no additional code as compared to the regular
> build.
>
> "PortGroup muniversal 1.0" defines a universal variant that builds multip
Has this list been added to the Guide?
> MacPorts defines a default universal variant that works with autotools
> configure scripts and some hand-made configure scripts.
>
> "use_configure no" declares that this port does not use any configure script,
> therefore MacPorts disables its default
On 21 Jul 2017, at 13:02, Umesh Singla wrote:
> Unless we have a snapshot of the previous state, that is, before it got
> hampered.
> But then again, we reinstall all the ports presently. At this time, it could
> be hard for me to detect what went wrong while sync or upgrade.
If I understood yo
