[KDE/Mac] Suggestion to set up a central MacPorts/KDE repository for easy exchange of MacPorts port files

mk-lists at email.de mk-lists at email.de
Sat May 10 14:04:39 UTC 2014

Hi folks,

I have set up a git repository on KDE’s infrastructure for hosting a MacPorts software tree
for tests of KDE software found on playground/SDK [1] which is backed up like all git.kde.org.
The tree is actually the portion below "trunk/ports", which is why e.g. the category kde is
already placed in the repo’s root.

Currently there is only the port konversation-devel, which I introduced for Eike Hein, who
agreed to work on a fix for current master.

I’d appreciate if you, Nicolas, would send the KDE 4.13 port files which I could/would
commit to this repo, so that e.g. Ian can pull them easily on his end, because he doesn’t
want to juggle around with Portfiles too much.

In order to make use of this MP software tree one simply has to clone it locally by e.g. 
$ mkdir ~/WC ; cd ~/WC
$ git clone git://anongit.kde.org/macports-kde MacPorts
$ cd MacPorts; ls
$ git log --oneline
9e5752d new port konversation-devel for testing git revision f8205a08
and insert that repo’s path in front of your default repo (assuming /Users/USER as the
user’s home directory) into /opt/local/etc/macports/sources.conf:
$ (cd /opt/local/etc/macports/; diff -u sources.conf.old sources.conf)
--- sources.conf.old	2014-05-10 15:33:41.000000000 +0200
+++ sources.conf	2014-05-10 15:33:57.000000000 +0200
@@ -28,4 +28,5 @@
 # For proper functionality of various resources (port groups, mirror
 # sites, etc.), the primary MacPorts source must always be tagged
 # "[default]", even if switched from the default "rsync://" URL.
 rsync://rsync.macports.org/release/tarballs/ports.tar [default]
See [2] for more details. Don’t forget to execute portindex in the /Users/USER/WC/MacPorts
directory whenever you add or remove a Portfile to that tree.

BTW, I usually name port files as Portfile.my, so that I’d have manually copy/rename them
to Portfile when I really want to enable the port locally. A run of portindex is of course
obligatory in such a case.

 ???	Shall we introduce the same here in order to avoid unwanted
 ???	collisions with standard-MacPorts or your own local ports ?

And, once again, this is just a suggestion for sharing Portfiles as well as patches
(which haven’t been committed upstream yet).


[1] https://projects.kde.org/projects/playground/sdk/macports-kde/repository
[2] https://guide.macports.org/chunked/development.local-repositories.html

More information about the kde-mac mailing list