Thanks for pointing this out.
Is it best to revert the unnecessary changes or simply note the problem for
future reference?
-Marcus
On Jun 9, 2014, at 6:37 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jun 9, 2014, at 4:14 PM, mcalh...@macports.org wrote:
Revision
120845
Author
Hello,
On Jun5, 2014, at 21:34, Eric Gallager eg...@gwmail.gwu.edu wrote:
Of those ports you mention, I currently only have kchmviewer installed
on my current machine, which I installed while testing different
chm-viewing applications. I generally use the Chmox port for those
purposes now
Please join us in welcoming the following new MacPorts committers:
- Christoph Erhardt (sicherha)
- Kurt Hindenburg (khindenburg)
- Daisuke Takahashi (dtakahashi)
- David Strubbe (dstrubbe)
We look forward to continued excellent contributions from these new team
members.
- Joshua, Rainer,
On Jun 8, 2014, at 8:26 PM, Daniel J. Luke dl...@geeklair.net wrote:
so, perl5.20 is out (and the new/current latest stable version)...
any chance we can get a little less crazy and just ship the 'current' perl
(instead of being perpetually behind)?
The current issues are:
1. We need a
The new version builds and appears to work correctly on 10.6. But see
below regarding 10.5.
On 2014-6-6 09:08 , Clemens Lang wrote:
Leopard:
certsync.m:162: warning: implicit declaration of function
‘SecPolicyCreateBasicX509’
I've provided an alternative implementation of the same behavior
On Jun 10, 2014, at 1:20 PM, Frank Schima m...@macports.org wrote:
On Jun 8, 2014, at 8:26 PM, Daniel J. Luke dl...@geeklair.net wrote:
so, perl5.20 is out (and the new/current latest stable version)...
any chance we can get a little less crazy and just ship the 'current' perl
(instead of
On Tue, Jun 10, 2014 at 7:20 PM, Frank Schima wrote:
1. We need a perl5.20 port. Difficulty: ?
It would be really nice if the perl5.X ports could be merged into a single
Portfile with subports so that new perl versions would be relatively easy to
add. All of the current perl ports seem to be
On Jun 10, 2014, at 2:21 PM, Mojca Miklavec mo...@macports.org wrote:
I would be really grateful if someone would be
willing to look into the above mentioned ticket. We would need a
slight modification of the configure/build scripts.
That change seems reasonable to me, but it would be
Can anyone state authoritatively which OS version and versions of Xcode
are currently being used on each of the MacPorts buildbots? Is this
documented anywhere? Do we have a stated policy on this matter and an
implementation mechanism?
I'm asking because I'm seeing different results between
On 2014-6-11 08:06 , David Evans wrote:
Can anyone state authoritatively which OS version and versions of Xcode
are currently being used on each of the MacPorts buildbots? Is this
documented anywhere? Do we have a stated policy on this matter and an
implementation mechanism?
Should be the
On 6/10/14 3:11 PM, Joshua Root wrote:
On 2014-6-11 08:06 , David Evans wrote:
Can anyone state authoritatively which OS version and versions of Xcode
are currently being used on each of the MacPorts buildbots? Is this
documented anywhere? Do we have a stated policy on this matter and an
On Tue, Jun 10, 2014 at 8:37 PM, Daniel J. Luke wrote:
On Jun 10, 2014, at 2:21 PM, Mojca Miklavec wrote:
I would be really grateful if someone would be
willing to look into the above mentioned ticket. We would need a
slight modification of the configure/build scripts.
That change seems
I (and I think Daniel Luke) just want to abolish all but the latest Perl.
We allow the installing of perls that have LONG since gone out of updates.
Perl goes out of its way to be backwards compatable. You have to do things
like use 5.16 to even use new features that break stuff.
Mark
—Mark
I sadly have not had enough time to work on cpan-mp, I've been mostly
learning the internals of macports first. But yeah, like I said on that
other thread, the latest perl is enough. Back when 5.x stalled because
everyone thought 6 was coming out it was ok to stay still. But now we get
new Perls
14 matches
Mail list logo
