Ports which use 'fetch.type svn' and have an https URL (eg, tickets #17419,
#18429, and possibly #18583) will quite likely fail for people in the fetch
stage. svn from the current subversion port (version 1.6.1) has the
--trust-server-cert option to avoid this, but /usr/bin/svn on 10.5 is too
old
On Wed, Apr 22, 2009 at 3:00 PM, kimura wataru kimu...@macports.org wrote:
I write experimental ruby_select for ruby186 and ruby18.
http://trac.macports.org/browser/users/kimuraw/ruby_select
I will test it shortly and try to add the ruby19 aspects to it.
Is it ok if I commit to your user
On Apr 24, 2009, at 02:45, Rainer Müller wrote:
Bryan Blackburn wrote:
Ports which use 'fetch.type svn' and have an https URL (eg,
tickets #17419,
#18429, and possibly #18583) will quite likely fail for people in
the fetch
stage. svn from the current subversion port (version 1.6.1) has
Ryan Schmidt wrote:
build.env isn't broken, but it isn't used if you override the
build phase, right?
Why not use the default build phase? Untested:
build.env ${configure.env}
build.cmd ./ROX-Filer/AppRun
build.args --compile ${configure.args}
If I use ${configure.env}, I get:
DEBUG:
On Apr 24, 2009, at 02:26, a...@macports.org wrote:
Revision: 50072
http://trac.macports.org/changeset/50072
Author: a...@macports.org
Date: 2009-04-24 00:26:05 -0700 (Fri, 24 Apr 2009)
Log Message:
---
build.env is broken, work around it
Modified Paths:
--
There is a follow-up report on SF.net saying that an additional patch
patch may also be needed:
https://sourceforge.net/forum/message.php?msg_id=7267196
But, again, I can not verify if that is so.
[1] http://trac.macports.org/ticket/19386
On Fri, Apr 24, 2009 at 7:57 PM, Uldis Bojars
Why was this universal_variant no? It builds universal here, and
making this not universal breaks building libsoup which is a headache
for gnome... so unless you want to !universal all of gnome, I suggest
the following:
Index: Portfile
I'm working on vtk-devel Portfile and I have:
a) completed a lengthy build of VTK
b) edited parts of the Portfile that affect downstream stages from the build
(ie, destroot command)
How can I continue with the downstream stages without losing the build?
The default behavior is to clean
Hi Florian,
On Fri, 24 Apr 2009 08:52:48 +0200, C. Florian Ebeling wrote:
On Wed, Apr 22, 2009 at 3:00 PM, kimura wataru kimu...@macports.org wrote:
I write experimental ruby_select for ruby186 and ruby18.
http://trac.macports.org/browser/users/kimuraw/ruby_select
I will test it shortly
Hi,
On Thu, 23 Apr 2009 00:02:30 +0200, Rainer Müller wrote:
kimura wataru wrote:
I write experimental ruby_select for ruby186 and ruby18.
http://trac.macports.org/browser/users/kimuraw/ruby_select
Will ruby19 be moved to ruby? Or what will happen to the existing ruby
port at all?
On Fri, Apr 24, 2009 at 01:37:48PM -0700, Darren Weber said:
I'm working on vtk-devel Portfile and I have:
a) completed a lengthy build of VTK
b) edited parts of the Portfile that affect downstream stages from the build
(ie, destroot command)
How can I continue with the downstream stages
First I want to apologize for being inactive in the last months.
I only have sporadic access to a Mac at the moment (I switched to
Linux with my main machine) so my activity was very low. But I
like the MacPorts project and will continue to update my ports
when I have time and access to my Mac.
On Apr 24, 2009, at 21:02, ma...@macports.org wrote:
Similarly, I've almost never looked at the chunked Guide. I load the
single-page Guide, so that I can press Command-F, type my search
string, press return, and find what I'm looking for. Which isn't to
say we shouldn't have the chunked
Has anyone else witnessed the default livecheck.regex failing when
using master_sites googlecode?
For me, it looks like there is style info and whitespace breaking the
pattern.
smime.p7s
Description: S/MIME cryptographic signature
___
14 matches
Mail list logo
