. :-)
+Additionally one should define a few (not necessarily global) presets
for working with your clone of the MacPorts repository:
+{{{
+$ git config --global push.default nothing
+$ git config --global branch.autosetuprebase always
+$ git config --global core.excludesfile ~/.gitignore_global
+$ git
> On Apr 18, 2016, at 7:43 AM, Mark Evenson wrote:
>
>
>
> On 2016/4/18 15:34, Macports wrote:
>>
>>> On Apr 18, 2016, at 4:34 AM, easie...@macports.org
>>> <mailto:easie...@macports.org> wrote:
>>>
>>> Revision
>&g
1cda66c841a548a07cc37e80b0727354b1236d9f374c7d44362acdb85eb3e1
> +checksums rmd160 95d5c0b79969d28d23b3330bb2fb5d4c94fe8919 \
> +sha256
> 08fc3b6c05c39fb975bba1f6dd49992df46511790ce8dc67398208af9565e199
>
> patchfiles patch-issue7845.di
Dear Nicolas,
I think you're aware of René's striving for getting KF5 to work in
MacPorts...
In the last 2 months or so I tried to catch up with his incredible pace
and thus
decided to at least come up with a minimal set of ports, which would
allow to
get started with KF5 on OS
1
[6] https://build.macports.org/changes/58439
[7] https://build.macports.org/changes/58440
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
t possible to have these
> reviewed and/or submitted?
>
> Kind regards,
>
> --
> Björn Ketelaars
> GPG key: 0x4F0E5F21
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge
${python.version}-setuptools
> +
> +depends_run-append port:py${python.version}-numpy
> +
> +livecheck.type none
> +} else {
> +livecheck.type regex
> +livecheck.url ${master_sites}
> +}
> Property changes on: trunk/dports/python/py-pyorick/Po
e they're meant to update the configure.args in this
> variant as well.
>
> Instead, just replace the one arg you care about with the new arg:
>
> configure.args-replace --without-guile --with-guile
See <https://trac.macports.org/ticket/45527#comment:14>
Cheers!
Frank
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
hould
> probably be marked as a legacy compatibility variant that does nothing but
> requires the qt4 variant.
>
> Consider using configure.args-replace instead of using configure.args-delete
> and configure.args-append.
>
> The qt5 variant should be marked as conflicting
reinplace to replace
>> the placeholder with its final value.
>
> You shouldn't even be able to write to ${filespath}, it just happens
> that (a) this is the destroot phase so we're running as root, and (b)
> you're using Tcl commands (as opposed to something run via system) so
> sandboxing isn't applied.
>
> That should be considered a bug in base, albeit not an easy one to fix.
I have made some adjustments in r133108.
Cheers!
Frank
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
ket, just wondering what is next to
> progress...
>
> John
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
36a0fb9873137514090849820e296eb7
Please reinstate the rmd160 checksum. Per the guide [1], we like to use both
rmd160 and sha256 checksums.
Cheers!
Frank
[1] <https://guide.macports.org/#reference.phases.checksum>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On 20 May 2014, at 01:10 , Ryan Schmidt wrote:
> I undid the revbump, to save users from needlessly reinstalling the port if
> they haven't already.
Oh, thanks, Ryan!
___
macports-dev mailing list
macports-dev@lists.macosforg
o solve this problem, but tiff's build system is horrible
> and is not making it easy for me. Here's the ticket under which I'm working
> on this:
> https://trac.macports.org/ticket/43642
I CC’ed myself to it.
Sorry revbumping for nothing.
Greets,
Marko
ibrary/Preferences/com.apple.dt.Xcode.plist to
/opt/local/var/macports/home/Library/Preferences
DEBUG: skipping ppc in
/opt/local/share/cmake-2.8/Modules/CPack.OSXScriptLauncher.in since this system
can't run it anyway
---> Scanning binaries for linking errors
Could not open /opt/X11/lib/libX11.6.dylib
orrectly, on a fresh MacPorts install
> having run only the 2nd command?
Yes:
---
$ ps aux | grep dbus
marko 634 0.0 0.0 2473220 1116 ?? S11:14AM 0:00.02
/opt/local/bin/dbus-daemon --nofork --session
---
E.g. all KDE apps run as they shoul
Hi,
when setting up a new MacPorts installation I noticed reading dbus’ notes:
---
$ port notes dbus
dbus has the following notes:
# Startup items have been generated that will aid in
# starting dbus with launchd
At least these two were needed here on my end:
—
$ sudo chmod o+r /opt/local/libexec/macports/lib/tcl8.5/.
$ sudo chmod o+r /opt/local/libexec/macports
—
but it looks like /opt/local/libexec/macports/lib/tcllib1.15
—
drwxr-x--x 111 root admin3774 May 11 16:22 tcllib1.15
—
is another candidate
u installed it? What are the
> permissions
> of /opt/local/libexec/macports/lib/tcl8.5?
—
$ ls -la /opt/local/libexec/macports/lib/tcl8.5/.
—
reports
—
drwxr-x--x 17 root admin578 May 11 16:22 .
—
> I'm fairly confident the Tcl Makefiles get this right by installing using
>
s it hasn’t gone forward unfortunately [2].
Wouldn’t be a “ticket” port command an alternative/complementary approach?
Greets,
Marko
[1] https://trac.macports.org/newticket
[2] https://lists.macosforge.org/pipermail/macports-dev/2013-October/024526.html
___
m
Hi Clemens,
this is what I get since I installed the current RC:
—
$ /opt/local/libexec/mpstats submit
Error: couldn't read file
"/opt/local/share/macports/Tcl/macports1.0/macports_fastload.tcl": no such file
or directory
—
Luckily I had seen http://trac.macports.org/changeset/1
gain,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
[1] https://bugs.kde.org/show_bug.cgi?id=316404
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
GPGMail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
penPGP using GPGMail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Hi Shree,
when I tried to add a comment to a ticket [1] I just got the response “Trac
Error” from MacPorts trac.
Since this happened a couple of times within the last 2 hrs or so I guess
something is wrong on the server side, because switching to another web client
didn’t help either.
Greets
Hi Frank,
thanks for pointing that out. I wasn’t aware of the stub!
I’ve reopened the ticket and am awaiting input from the portfile author.
Thanks again,
Marko
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev
I am not sure whether it had been already said, but I think it would be nice to
let query list also generate links to the port’s home URL, which holds just as
well for the MacPorts port list!
___
macports-dev mailing list
macports-dev
Dear Ryan,
thanks for your attentive eye, as always!
I am sorry I committed such messy ports with rkward(-devel), but I just
committed what I got from the original authors. I see now that the discussion
you had back then in [1] didn’t produce a fully MacPorts-satisfying portfile.
Well, I’ll
e want something like 'port echo installed and depends:someport'
> except recursive? That's probably going to be slow as things stand.
Oh, that’s a nice command: I haven’t much used such logic yet.
Greets,
Marko
___
macports-dev m
On 14 Apr 2014, at 02:09 , Ryan Schmidt wrote:
> These answers are in the OS X Mavericks software license agreement:
Thanks so much for your citation. I have stolen them right away and replanted
them on [1]
>> - How can he get in contact with the MacPorts CI guys?
> admin at ma
hat. :-)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
ited this kind of a response… I am paddling
back. :-)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
I looked at one of the binary packages
> (tiff-4.0.3_2.darwin_10.x86_64.tbz2) and did not see any obvious mislinking.
> Do you know why rev-upgrade decided to rebuild tiff on your system?
I have no clue.
The only idea I had was that I started the whole MacPorts installation from
scratch and
;ve never done any compilation on OSX).
and in my first reply [2] to his post I went through his list of tools and I
think MacPorts has everything in stock for the KDE CI system.
>- Can he virtualise Mac OS X legally on a Linux machine?
No. [3]
>- Must he invest in Apple hardware
am so pernickety. :-)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Hi devs,
I have found [1-6] discussing how licenses are being handled on MacPorts.
Browsing our Guide I couldn’t find any section containing license rules.
According to [7] we’ve got only port_binary_distributable.tcl [8] as some sort
of license documentation.
Shouldn’t we have more that our
org-libXcomposite, port:xorg-libXfixes
Runtime Dependencies: port:shared-mime-info, port:hicolor-icon-theme
—
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
ver and over
again to posts like mine. :-)
Perhaps a warning message would be nice and perhaps an option to enable/disable
searching for only-runtime deps.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Yesterday I noticed - while installing a MacPorts from scratch - that after all
the port tiff got rebuild by rev-upgrade.
Looks like tiff would need a revbump right?
How is the policy regarding such cases??
Shall one simply commit a revbump whenever one spots a port like that
-)
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
libiodbc
gtk2
gtk-doc
…
—
So, the question is, why the rdependants command didn’t spot this in the first
place?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman
Hi Eric,
> #!/bin/sh
> for depport in `port -q rdeps $1`; do
> sh /path/to/mp-distributable.sh ${depport}
> done
that worked like a breeze. I should have been able to create in on my own. :-)
Thanks!
Greets,
Marko
___
is mp-distributable.sh in order to determine whether
a port is binary-distributable.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
tests" is perhaps not so nice
during install, but at least it does what I intended to do.
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
might imply.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
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/listi
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 afte
Hi Ryan,
I do like your work very much! This looks really cool!!!
A few remarks:
1) Perhaps the icons at least could be blue to match the mandatory
good-old MacPorts icon, which definitely needs to appear here instead of the
new “macports”. :)
2) I think that the headline is
I also had problems with the git upgrades every now and then. Just a give it
some time and then all will run smoothly.
(Have no idea why it happens, though. Perhaps an issue with some mirrors… )
I usually tried some hours later once again.
___
macports
de-mac
:-/
KDE-DEVEL makes more sense:
https://mail.kde.org/mailman/listinfo/kde-devel
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
rko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
TERFACE_LIBRARIES:
This warning is for project developers. Use -Wno-dev to suppress it.
-- Generating done
-- Build files have been written to:
/Users/okram/WC/GIT/kmymoney.online-balance_highlighting_extended/build
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
tp://randa-meetings.ch/2014/02/19/randa-meetings-2014-the-date-is-set-please-register/
---
In various discussion threads during the last weeks the KDE community expressed
that they would welcome anyone willing to do some bridge-building between KDE
on Linux and OSX/MacPorts! KDE is considering to als
Search for Phonon
:info:configure -- -> PHONON_VERSION is 4.7.1
:info:configure -- -> PHONON_INCLUDE_DIR is /opt/local/include
:info:configure -- -> PHONON_LIBRARY is /opt/local/lib/libphonon.dylib
:info:configure Change Dir:
/opt/local/var/macports/build/_Users_okram_WC_MacPorts_ports_kde_
On 22 Mar 2014, at 18:01 , Ryan Schmidt wrote:
> On Mar 22, 2014, at 11:51, mk-macpo...@techno.ms wrote:
>> do MacPorts’ buildbots also build all debug variants of the various ports,
>> or only the default variant of every port?
> Only default variants.
I was afraid to hear
HI devs,
do MacPorts’ buildbots also build all debug variants of the various ports, or
only the default variant of every port?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo
did the job.
(And yes, you are right, the tests wouldn’t work if one would install the tests
someplace.
The test apps need to sit in the build directory in order to access additional
files outside it.
___
macports-dev mailing list
macports-dev@lists.mac
actually installed in the system and
not only built and removed again.
So, I’d like to know where to place which files below ${destroot}.
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman
Hi MacPorts devs,
how is the schedule for release of the next MP release which will - I gather -
include the opt-in-able mpstats?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman
s to be worked out first.
Yes, absolutely!
> Coming from the Linux kernel, pure git expects a pull-based workflow.
> One central instance pulls up changes from many other repositories into
> the main repository. I would rule out such a person-based pull model for
> MacPorts, as who wou
On 16 Mar 2014, at 19:42 , Sean Farley wrote:
> I would suggest Mercurial.
+1
But, in order to avoid any flamewars: I’d be going for git as well, if it would
win in an election. :-)
___
macports-dev mailing list
macports-dev@lists.macosforge.
application itself?!
I am new to this, so I don’t understand for a start why a URL is being
displayed with this app.
I figure I need to consult KDE’s developer mailing list regarding this one,
right?
Greets,
Marko
___
macports-dev mailing list
macports-dev
application itself?!
I am new to this, so I don’t understand for a start why a URL is being
displayed with this app.
I figure I need to consult KDE’s developer mailing list regarding this one,
right?
Greets,
Marko
___
macports-dev mailing list
macports-dev
/./:/opt/local/lib${DYLD_LIBRARY_PATH:+:$DYLD_LIBRARY_PATH}
"/Users/marko/projects/TestGraphical/build/src/testgraphical.app/Contents/MacOS/testgraphical"
"$@"
—
So, does this mean, that a system framework tries to use a library supplied by
MacPorts?
This is what otool te
From: mk-li...@email.de
Subject: Re: Running KDE apps on Apple OS X
Date: 11 Mar 2014 23:05:09 GMT+1
To: KDE-devel Mailing-List
Cc: KMyMoney KDE Development List , Developer-MacPorts
Mailing-List
Hi Ian,
thanks for your initiative!!!
I am not a software engineer - but just a Linux/MacOSX
,
Marko
[1] https://trac.macports.org/ticket/42160
[2] https://trac.macports.org/ticket/42404
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
ote that selfupdate will no longer do anything once you installed trunk.
> If you want to update your MacPorts installation you need to svn up your
> working copy of trunk and run the install process again.
So, he was only referring to macports base and NOT the whole MacPorts
insta
orm this stunt! No?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
> At that point, it might take as long as a reboot depending on your build: but
> you should achieve the same outcome.
I guess you’re right. :)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/m
Windows"-like! ;-)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
There is still one big problem with all of this, which is that a ton of daemons
and agents might be running as root or as another user for a given MacPorts
installation.
In case I want to swap in another installation, say a debug installation, I
would have to make sure that all these services
On 16 Feb 2014, at 21:46 , Jeremy Lavergne wrote:
> But I am assuming macports can handle being inside a symlink since I recall
> it can operate across drives.
Thanks, Jeremy.
That seems to be a good approach.
Greets,
Marko
___
macports-dev m
for every installation I should be able to make
sure that no file lands outside /opt/local !
Of course I have to assume that there are no rogue ports.
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.or
I just wanted to set up a 2nd parallel MacPorts install - as I used to have it
before moving to Mavericks…
Now I realise that it is probably not a good idea to have a setup like that
after all.
Some applications install themselves into /Applications and have settings in
/Library…
Assuming I
Hi Clemens,
On 10 Feb 2014, at 12:01 , Clemens Lang wrote:
> You can just install trunk right over your old installation… Note that
> selfupdate will no longer do anything once you installed trunk. If you want
> to update your MacPorts installation you need to svn up your workin
Hi,
I would like to try MacPorts’ current trunk version.
How do I do this seamlessly, i.e. is it necessary to reinstall MacPorts from
scratch, or can I somehow manage to keep all installed ports in place while
just switching from my existing installation to trunk??
Greets,
Marko
make sense to handle cases like that differently?!
And, do I need trunk to be able to run mpstats?
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
> The problem here is that the aqbanking Portfile violates lint:
Oh, good to know.
Can be fixed. :)
Will do so right away.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
rt is replaced_by or
simply non-existing?!
Greets,
Marko
[1] http://stats.macports.neverpanic.de/ports/search/name/aqbanking
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On 09 Feb 2014, at 20:42 , Jeremy Lavergne wrote:
> You probably need to run trunk for access to POST, which isn’t available in a
> release yet.
Ooops, I see. I wasn’t aware of that trunk is a must for this feature.
___
macports-dev mailin
ting
"curl post "submission\[data\]=$json" $stats_url"
—
What can be done about this?
Greets,
Marko
_______
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On 14 Jan 2014, at 03:02 , Ryan Schmidt wrote:
> Perhaps you could contribute to resolving the MacPorts VirtualBox ticket
> then.
I am afraid my knowledge about setting up a proper virtualbox installation is
not sufficient for this endeavour.
I tried a while ago though.
Ticket #41392
my system once I upgrade or remove the
software. That’s why I like MacPorts. :-)
BUT, I guess, this is my only option left now. :-/
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
erformance
> degradation.
>
> I recommend you delete the cache directory entirely
>
Thanks, Clemens, for the hint.
I did so and it has solved the issue:
markos-imac:5396pzbj3gq7s1hwf2shczvm0000gq marko$ l
total 0
drwxr-xr-x 4 macports macports 136 Jan 13 00:04 ./
drwxr-xr-x 3
On 12 Jan 2014, at 22:41 , Chris Murphy wrote:
> Maybe. Try adding -usbdevice tablet to the qemu command line.
That made my trackpad almost unusable. :-(
But it didn’t change anything.
No progress during the system probe step.
___
macports-
OK, now I found out using “info usb” that USB support is NOT enabled by default.
So, perhaps that is the problem?
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
ue to
>> the missing kvm implementation.
> I see it uses Xen or KVM, but the fact you're getting this far, well past the
> kernel and initramfs being loaded, seems like it is working.
Well, a lot seems to work, indeed. But unfortunately I can’t get beyond the USB
device recognition
^
:info:build 1 error generated.
:info:build make[3]: *** [aqdb_db.lo] Error 1
—
I figure that these missing cache files don’t stop clang from working
correctly, but I wonder why this permission error occurs. Is my portfile
wrongly set up for clang for some reason?
Greets,
Marko
__
ure is searching for USB devices FOREVER,
unfortunately.
So, I guess qemu isn’t a true alternative to virtualbox on MacOSX, due to the
missing kvm implementation.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/m
initialize libusb: -99
—
Don’t know though whether this was due to the rescue system itself or due to a
the qemu emulation.
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
qemu is horribly slow or it is not able to successfully find USB devices
for it at all.
:-(
Greets,
Marko
P.S.: qemu likes to use kvm under Linux... Is this not supplied on MacOSX?
[1] https://trac.macports.org/ticket/41392
___
macports-dev mailing
make MacOSX’s
launchpad realise the vanishing of the two files? ;)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Hi Craig,
On 30 Dec 2013, at 15:57 , Craig Treleaven wrote:
> Yes, that would be expected behaviour. MacPorts has no way of
> knowing that the link was created so it ends up pointing to a
> now-deleted file after an uninstall.
ah, okay. I wasn’t sure, that’s why I asked. I thought t
Hi Craig,
after deinstallation of mythtv-core.27 I realised on 10.9 that
Myth_Filldatabase and Myth_Frontend stay behind in one of LauchPad’s MacPorts
application folders although they are invalid links.
Is this normal behaviour or a glitch in the deinstallation phase?
Greets,
Marko
have just done it… :-)
Thanks.
BTW, for all users who do not have an empty root password I suggest using
option “-p” here:
/opt/local/lib/mysql5/bin/mysql_tzinfo_to_sql /usr/share/zoneinfo |
mysql5 -u root -p mysql
:-)
___
macports-dev mai
could describe how and with which permissions you set
this user up in your case.
Thanks in advance and thanks for the great job you’ve done with bringing this
to MacPorts.
I am looking forward to test the suite.
Greets,
Marko
___
macports-dev mailing
esponding.
:-)
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
…
I am using the kde4 portgroup for that port.
Any hint for me?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
1 - 100 of 282 matches
Mail list logo
