On Thu, Oct 29, 2015 at 4:09 PM, Rainer Müller wrote:
> On 2015-10-27 22:24, Marko Käning wrote:
>> Hi Nicolas,
>>
>> while building kdevelop and kdepim4 I came across some rev-upgrades… Thus I
>> have rebumped ports kate, libkgapi and konversation.
>>
>> For instance, the latter tried to find
On 2015-10-27 22:24, Marko Käning wrote:
> Hi Nicolas,
>
> while building kdevelop and kdepim4 I came across some rev-upgrades… Thus I
> have rebumped ports kate, libkgapi and konversation.
>
> For instance, the latter tried to find libqca in it’s old location
> ---
> Dyld Error Message:
>
Hi,
I'm getting some weird results with the livecheck with respect to gate:
> port info gate
gate @7.1_4 (science)
...
> port -v livecheck gate
gate seems to have been updated (port version: e657ed0c, new version: v7.0)
This is the relevant part of the code that apparently confuses the
On Thu, Oct 29, 2015 at 4:55 PM, Jeremy Lavergne wrote:
> On Thu, October 29, 2015 11:47, Mojca Miklavec wrote:
>>
>> I'm getting some weird results with the livecheck with respect to gate:
>>
>>> port info gate
>> gate @7.1_4 (science) ...
>>
>>> port -v livecheck gate
>> gate seems to have been
> On Oct 29, 2015, at 11:09 AM, Rainer Müller wrote:
>
> What was the reason for moving Qt4 into its own prefix? I guess this is
> about allowing Qt4 and Qt5 to be installed at the same time?
>
> I only noticed this now, but it seems this change will cause problems:
>
> *
On 2015-10-29 16:47, Mojca Miklavec wrote:
> I'm getting some weird results with the livecheck with respect to gate:
>
>> port info gate
> gate @7.1_4 (science)
> ...
>> port -v livecheck gate
> gate seems to have been updated (port version: e657ed0c, new version: v7.0)
>
> This is the relevant
Ohoh, so this is finally where I get to say "I told you so"?
@Michael Dickens wrote:
> qtscriptgenerator is having issues with locating phonon now that it's
> not co-located with the qt4 install. Like QCA, it might make sense to
> just co-locate phonon into the new qt4 install prefix.
Yeah, and
On Thu, Oct 29, 2015 at 5:28 PM, Rainer Müller wrote:
> On 2015-10-28 20:20, Mojca Miklavec wrote:
>> Apart from the fact that I don't know how to get a binary called
>> "f2py" (it would be nice to have the executable without the extension
>> available), running
>>
On Thu, Oct 29, 2015 at 6:02 PM, Rainer Müller wrote:
> On 2015-10-29 17:05, Mojca Miklavec wrote:
>>
>> When 10.11 came out (where Qt 4 no longer worked), the
>> switch to Qt 5 and moving Qt 4 away suddenly had to be done in a
>> hurry, so the maintainer decided for the easier path to simply put
On 2015-10-28 20:20, Mojca Miklavec wrote:
> Apart from the fact that I don't know how to get a binary called
> "f2py" (it would be nice to have the executable without the extension
> available), running
> f2py-3.5 -c fib1.f -m fib1
> fails to find the Fortran compiler as it looks for gfortran
Here's my take: Qt4 needed to be moved out of the way to be installable
in parallel with Qt5, and, by moving everything into a location where
you have to know where it is, we really test the build systems for those
ports that use Qt4/5. Many ports, generally those that use the qt4 or
qmake
- On 27 Oct, 2015, at 22:51, Clemens Lang c...@macports.org wrote:
> I didn't see this in my test runs, but maybe I just overlooked it. I guess we
> should just add that path to the trace whitelist, because it's basically
> /usr/bin or /bin anyway.
Should be fixed in r141852.
--
Clemens
Michael Dickens wrote:
> qmake PortGroups, just needed a rev-bump. Some ports such as phonon
> install files that =assume= the same install prefix as Qt, and so when
> they are installed elsewhere everything breaks down for ports that
> depend on them (e.g., using qmake to find phonon fails
On 2015-10-29 17:38, Mojca Miklavec wrote:
> On Thu, Oct 29, 2015 at 5:28 PM, Rainer Müller wrote:
>> On 2015-10-28 20:20, Mojca Miklavec wrote:
>>> Apart from the fact that I don't know how to get a binary called
>>> "f2py" (it would be nice to have the executable without
On 2015-10-30 03:28 , Rainer Müller wrote:
> On 2015-10-28 20:20, Mojca Miklavec wrote:
>> Apart from the fact that I don't know how to get a binary called
>> "f2py" (it would be nice to have the executable without the extension
>> available), running
>> f2py-3.5 -c fib1.f -m fib1
>> fails to
15 matches
Mail list logo