On 2014-04-10 22:02, mk-macpo...@techno.ms wrote:
> How can I keep my needed patches for MacPorts base without the need to
> re-patch base after the selfupdate call?
Note that this patch is not for base, but for the ports tree that is
distributed as a rolling release. The MacPorts base would be t
On 10 Apr 2014, at 22:09 , Jeremy Lavergne wrote:
> You probably need add a local repo with higher priority, such as:
Looks like it. :)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports
You probably need add a local repo with higher priority, such as:
http://trac.macports.org/wiki/howto/SyncingWithSVN
Note the repo needs at least:
dports/_resources/ for the PortGroups, and
dports/devel/cmake/ for cmake
On Apr 10, 2014, at 16:02, mk-macpo...@techno.ms wrote:
> Hi MP devs,
>
>
Hi MP devs,
currently I have to have patch [1] in place to be able to successfully install
qmake-based ports.
The problem is now that during "sudo port selfupdate” all these changes get
reverted.
How can I keep my needed patches for MacPorts base without the need to re-patch
base after the se
