On Dec 23, 2014, at 4:48 PM, Mihai Moldovan wrote:
> There's no technical reason. normalize and resolve operate on the
> (shared) original path. I don't really get your question, though. What
> would you have done differently?
Originally I was just thinking about reorganizing the code, but after
On Dec 24, 2014, at 5:45 PM, René J.V. Bertin wrote:
>
> I'm wondering about the port, though. I saw that libpgf appears to be part of
> something called pgf which isn't the same thing already present as port:pgf .
> I hope there's no unwritten rule that states I should propose a port for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 25.12.2014 12:45 AM, René J.V. Bertin wrote:
> Yess, that was it. It's possible that I hadn't yet added a version number
> when I portindexed it, and
never repeated the operation because that doesn't appear to be necessary for
version bumps.
Ac
On Wednesday December 24 2014 15:07:40 Ryan Schmidt wrote:
Hi,
> Any port install will first try to upgrade dependencies.
Yeah, that's what I also realised thinking about it some more (and then saw it
confirmed when `-n` had the intended effect).
>
> Off the top of my head I don't see a probl
On Dec 24, 2014, at 4:57 AM, René J.V. Bertin wrote:
> On Wednesday December 24 2014 01:39:23 René J.V. Bertin wrote:
>>
>> Attached is a draft for a port:libpgf portfile, basically following Gilles
>> Gaulier's instructions at
>> https://projects.kde.org/projects/extragear/graphics/digikam/di
Ryan Schmidt writes:
>> On Dec 23, 2014, at 6:42 PM, s...@macports.org wrote:
>>
>> Revision
>> 129987
>> Author
>> s...@macports.org
>> Date
>> 2014-12-23 16:42:44 -0800 (Tue, 23 Dec 2014)
>> Log Message
>>
>> boost: update to 1.57; closes #46156
>
>> Modified: trunk/dports/devel/boost/Portfil
On Wednesday December 24 2014 01:39:23 René J.V. Bertin wrote:
> Hello,
>
> Attached is a draft for a port:libpgf portfile, basically following Gilles
> Gaulier's instructions at
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/mast
On Wednesday December 24 2014 21:47:11 Ian Wadham wrote:
> > Without having really looked at the code, have you tried NOT doing that
> > (possibly after checking whether it has the required privileges)?
>
> I did, but the KDE ReviewBoard jockeys pooh-poohed that. In the end I
> modified
Well,
On 24/12/2014, at 9:27 PM, René J.V. Bertin wrote:
> On Wednesday December 24 2014 21:16:54 Ian Wadham wrote:
>> The code always seems to work OK if the crash procedure in the failed
>> program starts Dr Konqi by forking. But it never works (on Apple OS X)
>> if the crash procedure contacts an i
On Wednesday December 24 2014 21:16:54 Ian Wadham wrote:
Morning!
> The code always seems to work OK if the crash procedure in the failed
> program starts Dr Konqi by forking. But it never works (on Apple OS X)
> if the crash procedure contacts an independent process (kdeinit4) via
> a socket an
On 24/12/2014, at 8:52 AM, Joshua Root wrote:
> On 2014-12-24 08:15 , Ian Wadham wrote:
>> Hi Clemens,
>>
>> On 23/12/2014, at 11:33 PM, Clemens Lang wrote:
>>> - On 23 Dec, 2014, at 13:02, René J.V. Bertin rjvber...@gmail.com wrote:
IIRC, OS X no longer allows setuuid/setguuid, or only
Hi,
To keep the highly productive contributors stay motivated, I would
like to ask other committers to help reviewing Julien's patches:
http://trac.macports.org/query?status=!closed&reporter=jul_bsd%40yahoo.fr
>From what I've seen so far these are high quality patches, but he had
to add a lot of
12 matches
Mail list logo
