Re: El Capitan migration

I can confirm that following the instructions for an uninstall and then doing an install from source worked perfectly fine with both the El Capitan GM and Xcode 7 GM. My first at

Re: El Capitan migration

On Sep 14, 2015, at 08:27, Joseph C Slater, PhD, PE wrote: > Is El Capitan migration "working" properly? I have not tried migrating to El Captian yet (I installed El Capitan beta on a separate disk), but I don't know of any reasons why it would be different from previous versions in regard to m

Re: Versions in ports

On Sep 14, 2015, at 09:22, Artur Szostak wrote: > > After about a year's worth of experience with MacPorts, there is something > that I still do not understand: why is there no mechanism to express version > requirements in the dependency information for a Portfile? Because MacPorts does not ha

Re: ledger fails to build on yosemite

> On Sep 14, 2015, at 6:08 AM, Kurt Hindenburg wrote: > > >> On Sep 13, 2015, at 1:37 AM, Kastus Shchuka wrote: >> >> I attempted to install ledger on yosemite (10.10.5) but it failed. I found >> ticket https://trac.macports.org/ticket/47597 with a log which looks very >> similar to mine. T

Re: Versions in ports

> On Sep 14, 2015, at 12:44 PM, Artur Szostak wrote: > A 1.0 depends on C 1.0 > B 1.0 also depends on C 1.0 > > And their newer versions are not backwards compatible with C 1.0, thus: what is the nature of this incompatibility? > A 2.0 depends on C 2.0 > B 2.0 depends on C 2.0 > > If the follo

RE: Versions in ports

> ... information of Portfiles, it is impossible to make the following command > unsafe: ... I mean, safe, it is impossible to make the command safe. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailma

RE: Versions in ports

>> […] A normal upgrade will first upgrade all the ports >> dependencies, as required, such that you end up with a consistent >> updated port. Only if you specifically disable this can you get into a >> mess. > > But if ports A and B both depend on port C, and you run “port upgrade > A”, then it wi

RE: Versions in ports

>> Then why not protect all other upgrade operations with a -f | --force >> flag, except when upgrading everything? It seems much too easy at the >> moment to perform an upgrade operation that has a good chance of leading >> to an inconsistent state. > > no it will not. A normal upgrade will first

Re: Versions in ports

Chris Jones wrote: […] A normal upgrade will first upgrade all the ports dependencies, as required, such that you end up with a consistent updated port. Only if you specifically disable this can you get into a mess. But if ports A and B both depend on port C, and you run “port upgrade A”, the

Re: ledger fails to build on yosemite

Kastus Shchuka wrote: I attempted to install ledger on yosemite (10.10.5) but it failed. I found ticket https://trac.macports.org/ticket/47597 with a log which looks very similar to mine. The ticket contains a patch which does not seem to be committed to the port yet. Please excuse my ignoranc

Re: Versions in ports

On 14/09/15 15:49, Artur Szostak wrote: Then why not protect all other upgrade operations with a -f | --force flag, except when upgrading everything? It seems much too easy at the moment to perform an upgrade operation that has a good chance of leading to an inconsistent state. no it will not

RE: Versions in ports

Then why not protect all other upgrade operations with a -f | --force flag, except when upgrading everything? It seems much too easy at the moment to perform an upgrade operation that has a good chance of leading to an inconsistent state. From: Brandon Allbery [

Re: Versions in ports

On Mon, Sep 14, 2015 at 10:22 AM, Artur Szostak wrote: > To me, it feels like the MacPorts documentation is misleading the end user > to believe that upgrading/downgrading individual packages is a routine and > safe procedure, when my experience tells me otherwise. Can anyone point me > to the re

Versions in ports

Hi, After about a year's worth of experience with MacPorts, there is something that I still do not understand: why is there no mechanism to express version requirements in the dependency information for a Portfile? I have been running into a number of situations where upgrading or downgrading a

El Capitan migration

Is El Capitan migration "working" properly? I updated to the GM recently and the macport installations I use seem to work fine, however port selfupdate gave "Error: Current platform "darwin 15" does not match expected platform "darwin 14" Error: If you upgraded your OS, please follow the migra

Re: Error when starting python3

> On 14/set/2015, at 05:55, Glenn Ramsey wrote: > > Hi All, > > I get this error when starting python3: > > $ python3 > Python 3.5.0rc4 (default, Sep 14 2015, 13:58:59) > [GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin > Type "help", "copyright", "credits" or "license" for mo