On 13/03/2013, at 11:07 AM, Nicolas Pavillon wrote:
That's interesting, because there was a discussion some days ago about
keeping (or not) kde3 in macports after its deprecation. I did not try to
install kdelibs3 for a long time (essentially due to the conflict with kde4),
though. The
Hi Ian,
On Mar 14, 2013, at 7:47 AM, Ian Wadham wrote:
Is it possible to do something similar on Macports and remove the conflicts
with
restriction on KDE 3 and Qt 3, or is there some more fundamental problem, such
as qt4-mac is native to Mac OS X desktop and qt3 is not?
a while back KDE3
+if {${configure.compiler} != clang ${os.platform} == darwin} {
+depends_build-appendport:clang-3.1
+configure.compiler macports-clang-3.1
+}
So... if the user asks for clang-3.2, you give them clang-3.1 instead?
You should probably use compiler.blacklist instead to
On Mar 12, 2013, at 11:31 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Mar 12, 2013, at 11:28 AM, Michael Dickens michae...@macports.org wrote:
I think this hook is a great addition to the muniversal PortGroup.
Nice!
Can I commit this change? Or, do y'all want/need some time to think
From what I can remember, what made this possible was:
- Separate and unique naming of KDE and Qt libraries, with links such as
qt3.so
to the latest versions of the basic XXX 3 and XXX 4 libraries and
binaries.
- Separate areas in $HOME (equivalent to
On Tue, Mar 12, 2013 at 7:47 AM, Ryan Schmidt ryandes...@macports.org wrote:
Notes shouldn't introduce manual line breaks in the middles of sentences;
when displayed, MacPorts inserts line breaks into the notes automatically for
you where appropriate for the current width of the terminal
On Mar 14, 2013, at 9:38 AM, h...@macports.org wrote:
Revision: 104065
https://trac.macports.org/changeset/104065
Author: h...@macports.org
Date: 2013-03-14 06:38:50 -0700 (Thu, 14 Mar 2013)
Log Message:
---
kytea: update to 0.4.4; use g++ instead of clang.
On Mar 14, 2013, at 9:32 AM, Nicolas Pavillon ni...@macports.org wrote:
Using compiler.blacklist could sound good, but frankly, it is not always very
encouraging to use fully undocumented commands. Until you mentioned it, I did
not even know the fallback additional command, with which I
Hi,
Could a committer please take a look at the two related tickets
https://trac.macports.org/ticket/38341
https://trac.macports.org/ticket/38344
The second depends on the first, which is an update to a port for which the
maintainer has not responded.
cheers Chris
smime.p7s
Description:
On Mar 14, 2013, at 12:40, Lawrence Velázquez wrote:
On Mar 14, 2013, at 9:32 AM, Nicolas Pavillon wrote:
After testing the blacklist command, one thing I could not really understand
is that putting
compiler.blacklist apple-gcc-4.2
in the Portfile, and then running
sudo port -ds
It's not a harfbuzz-specific problem. It's already fixed globally in MacPorts
base and it will be in MacPorts 2.2. Until that's released, use the workaround
I posted in the ticket.
On Mar 14, 2013, at 13:51, Peng Yu pengyu...@gmail.com wrote:
Should harfbuzz build use a random directory
On Mar 14, 2013, at 12:20, Lawrence Velázquez wrote:
On Mar 14, 2013, at 9:38 AM, h...@macports.org wrote:
Revision: 104065
https://trac.macports.org/changeset/104065
Author: h...@macports.org
Date: 2013-03-14 06:38:50 -0700 (Thu, 14 Mar 2013)
Log Message:
---
On Mar 14, 2013, at 08:30, michae...@macports.org wrote:
Revision: 104063
https://trac.macports.org/changeset/104063
Author: michae...@macports.org
Date: 2013-03-14 06:30:46 -0700 (Thu, 14 Mar 2013)
Log Message:
---
log4cpp:
* update to version 1.1;
* redo
This is most likely a problem with the $PATH variable in case of application
bundles, as launching it from the command line
(running /Applications/MacPorts/KDE4/krusader.app/Contents/MacOS/krusader
from the Terminal if default path) seem to
work fine.
I am not sure if there would be an
14 matches
Mail list logo
