[KDE/Mac] How can I change one piece of code in a MacPorts installation?

Nicolas Pavillon nicos at macports.org
Mon Jul 21 13:41:21 UTC 2014


Marko already covered several things, but I just would like to add another approach which has been helpful to me sometimes. The local repositories are a very useful way to patch up code, but in the case you have several tests to make, it can be pretty cumbersome, as you have to rebuild everything from scratch each time, with your new patches. 
Another way to avoid rebuilding everything is to use lower-level Macports commands, to avoid the fact that a new clean copy of your gets extracted each time, with a clean at the end of the install. You can run “port extract” to get a copy, change the code with patches or manually, and then run “port activate” to install the port, but normally without the cleaning stage, so that you keep the copy of the code.



On Jul21, 2014, at 17:28, Ian Wadham <iandw.au at gmail.com> wrote:

> Hi Marko,
> On 21/07/2014, at 3:50 PM, Marko Käning wrote:
>> On 21 Jul 2014, at 05:43 , Ian Wadham <iandw.au at gmail.com> wrote:
>>> What I am wondering is whether there is some way I could edit
>>> the KCrash source-code, rebuild kdeui library or the whole of
>>> kdelibs4 and then install it down in MacPorts (/opt/local)?
>> well, I had promised to keep the MacPorts/KDE repository up to date
>> with your KCrash patches, but I was swamped with KF5 work, which is
>> why I hadn’t done that yet.
>> Now I see that you indeed have a real need for those patches in
>> MacPorts. So, I’ll do this right away. Give me half an hour to test
>> this.
>> Apart from that I suggest you check out MacPorts’ Guide regarding
>> setting up local portfile repositories [1] or my comments in [2].
>> In any case, please clone the MacPorts/KDE repo [3] where I’ll
>> push your patches to in a few minutes.
>> Greets,
>> Marko
>> P.S.: If you were present on IRC we could discuss more directly. ;)
>> [1] https://guide.macports.org/#development.local-repositories
>> [2] https://projects.kde.org/projects/playground/sdk/macports-kde/repository/revisions/master/entry/README.txt
>> [3] https://projects.kde.org/projects/playground/sdk/macports-kde
> Thanks very much for all this info and the patches and the macports-kde
> repository.  I have now managed to do sudo port upgrade on kdelibs4
> and got it to build with the amended KCrash code.
> At first sight, it looks as though KCrash has never been able to start
> Dr Konqi by sending a message on a socket to kdeinit4.  I still get the
> same "connect" error and it starts Dr K by forking it.  But I need to get
> some more log messages into the code to prove exactly what is going
> on down there…
> Thanks again, Marko.  And now that I can understand the technique
> for inserting local test patches into MacPorts, I can investigate other
> mysteries, such as why kdeinit4 does not start kded4 automatically
> on Apple OS X.  It is supposed to.
> Cheers, Ian W.
> _______________________________________________
> kde-mac at kde.org
> List Information: https://mail.kde.org/mailman/listinfo/kde-mac
> KDE/Mac Information: http://community.kde.org/Mac

More information about the kde-mac mailing list