On Jun 6, 2009, at 04:08, t...@macports.org wrote:
Revision: 51915
http://trac.macports.org/changeset/51915
Author: t...@macports.org
Date: 2009-06-06 02:08:48 -0700 (Sat, 06 Jun 2009)
Log Message:
---
SnowLeopard default was set back to gcc-4.2, no need to explicitly
On Jun 6, 2009, at 15:28, Jeremy Lavergne wrote:
On Jun 6, 2009, at 1:09 PM, Bradley Giesbrecht wrote:
What is the macports way to get python26 into my paths?
python2.6 installed by MacPorts is already in your path. To get a
symlink called python pointing to it, use python_select as
On Jun 7, 2009, at 03:03, Joshua Root wrote:
On 2009-6-7 17:43, Bryan Blackburn wrote:
Looks like /Library is considered to be not a violation, so no
need for
destroot.violate_mtree.
This will be changing in 1.8, however.
I noticed your recent commit that removed this exemption. So how
On Jun 6, 2009, at 13:43, vincent habchi wrote:
For those who are in a hurry, here are Portfiles corresponding to
the brand new releases of Sip (first file) and PyQt – the latter at
last compatible with qt 4.5.1. Universal builds are supported,
though of course Sip must be built universal
--On 6 June 2009 12:43:36 -0700 Jordan K. Hubbard j...@apple.com wrote:
and if there are no users of a port to report errors, then who really
cares if it's broken?
All the users who come to MacPorts, give it a go, then go away without
reporting the errors that cause them to give up. It's
Hi Ryan,
New portfiles should typically be contributed by filing a ticket in
the issue tracker and attaching the new portfile there.
http://guide.macports.org/#project.tickets
Ok, I'll do that. Sorry for the noise.
Also, as soon as the software are released, I'll be adding a couple of
On Jun 8, 2009, at 12:26 AM, Ryan Schmidt wrote:
On Jun 6, 2009, at 04:08, t...@macports.org wrote:
Revision: 51915
http://trac.macports.org/changeset/51915
Author: t...@macports.org
Date: 2009-06-06 02:08:48 -0700 (Sat, 06 Jun 2009)
Log Message:
---
SnowLeopard default
On 2009-6-9 02:03, Blair Zajac wrote:
On Jun 8, 2009, at 3:01 AM, Joshua Root wrote:
On 2009-6-8 19:01, Ryan Schmidt wrote:
On Jun 7, 2009, at 03:03, Joshua Root wrote:
On 2009-6-7 17:43, Bryan Blackburn wrote:
Looks like /Library is considered to be not a violation, so no need
for
On Jun 8, 2009, at 14:54, vincent habchi wrote:
thank you for all your advice. I clearly copied the portfile of the
old versions, converted them to my own conventions (e.g. tabs
instead of spaces) and then tested them. They were by no means
meant to be drop-in replacement for the old
On Jun 6, 2009, at 15:36, Jeremy Lavergne wrote:
http://portmill.florianebeling.com/ is doing a default build for
all ports if I'm not mistaken.
I'm just getting back to this thread.
Thank you for your work on this, Florian!
Some friendly criticism:
I imagine you've been working on this
On Jun 8, 2009, at 2:18 AM, Ian Eiloart wrote:
So, and automated test suite would (a) get errors diagnosed and
fixed quicker, (b) reduce the number of errors as a result, and (c)
give us a way of flagging them before a user starts a 20 minute
build process.
I have been reading this
On Jun 8, 2009, at 15:49, Scott Haneda wrote:
On Jun 8, 2009, at 2:18 AM, Ian Eiloart wrote:
So, and automated test suite would (a) get errors diagnosed and
fixed quicker, (b) reduce the number of errors as a result, and
(c) give us a way of flagging them before a user starts a 20
minute
On Jun 8, 2009, at 5:46 PM, Ryan Schmidt wrote:
It is also a very good way to get an exact idea of what ports are
being installed. You can then see that port x has been installed
400 times, 390 of those with no issues, 10 of those with some issue.
I proposed this two years ago but was shot
On Mon, Jun 08, 2009 at 03:36:21PM -0500, Ryan Schmidt said:
[...]
You said you wrote this with Rails and CouchDB. While I understand the
desire to write using technologies you're familiar with, MacPorts is
written in Tcl, and the main MacPorts web site is written in PHP and
MySQL, and it
I'll take on the rewriting to PHP this summer if it needs to be done.
On Jun 8, 2009, at 7:54 PM, Bryan Blackburn wrote:
Of course it doesn't really lower the barrier if someone knows Rails
but not
PHP, especially when quite a bit of code has already been written.
While
trying to stay
On Mon, Jun 08, 2009 at 02:29:16PM -0700, jerem...@macports.org said:
Revision: 52043
http://trac.macports.org/changeset/52043
Author: jerem...@macports.org
Date: 2009-06-08 14:29:15 -0700 (Mon, 08 Jun 2009)
Log Message:
---
texlive_base: Use freetype instead of
2009/6/8 Scott Haneda talkli...@newgeo.com:
On Jun 8, 2009, at 2:46 PM, Ryan Schmidt wrote:
I proposed this two years ago but was shot down because this was considered
an
invasion of privacy and people didn't want MacPorts phoning home. I had
wanted
to have a nice status display on the
There's a difference between a crash and a failed compilation in that
the system can't just catch it. Apple also pays people to look at
those crash reports.
We're almost entirely unpaid volunteers with a variable body count.
On Jun 8, 2009, at 8:26 PM, Andre Stechert wrote:
If a program
xdvi can use either motif or xaw. It builds binaries for both if both
are available.
xdvi-motif.bin is the file that actually links against it.
--Jeremy
On Jun 8, 2009, at 17:01, Bryan Blackburn wrote:
On Mon, Jun 08, 2009 at 02:29:16PM -0700, jerem...@macports.org said:
Revision: 52043
On 6/8/09 4:56 PM, Jeremy Lavergne wrote:
I'll take on the rewriting to PHP this summer if it needs to be done.
And I'll volunteer to help with the Rails upkeep if not. =]
--j
On Jun 8, 2009, at 7:54 PM, Bryan Blackburn wrote:
Of course it doesn't really lower the barrier if someone
On 6/8/09 6:17 PM, Jim Meyer wrote:
On 6/8/09 2:46 PM, Ryan Schmidt wrote:
It is also a very good way to get an exact idea of what ports are
being installed. You can then see that port x has been installed 400
times, 390 of those with no issues, 10 of those with some issue.
I proposed this
Is there any plan to define or redefine the default compiler for Snow
Leopard?
Some folks may have access to a developer preview of Snow Leopard soon, what
do you recommend to maintain the integrity of an existing MacPorts
installation under Leopard, after the upgrade to Snow Leopard?
Take care,
On Jun 8, 2009, at 10:22 PM, Darren Weber wrote:
Is there any plan to define or redefine the default compiler for
Snow Leopard?
Some folks may have access to a developer preview of Snow Leopard
soon, what do you recommend to maintain the integrity of an existing
MacPorts installation
I have the most basic of a port file and I can not get it to work.
Here is how I do it by hand
cd ~/Downloads/rbldnsd
sudo -s
./consigure
make
cp rbldnsd var/rbldnsd
I am done at that point.
sudo port -d install in my local repo
DEBUG: Assembled command: 'cd /opt/local/var/macports/build/
Check out this command for ideas on why prefix isn't working:
./configure --help
If you need to override the configure arguments in MacPorts, that's
done via configure.args-append and configure.args-delete
On Jun 9, 2009, at 1:43 AM, Scott Haneda wrote:
I have the most basic of a port
I tried configure.args-delete, do I have to quote it?
configure.args-delete --prefix=/opt/local
Thanks
On Jun 8, 2009, at 10:46 PM, Jeremy Lavergne wrote:
Check out this command for ideas on why prefix isn't working:
./configure --help
If you need to override the configure arguments in
My apologies: the prefix is located in configure.pre_args. Please try:
configure.pre_args-delete --prefix=/opt/local
I believe you shouldn't need to quote it unless there's a space in it.
On Jun 9, 2009, at 1:54 AM, Scott Haneda wrote:
I tried configure.args-delete, do I have to quote it?
27 matches
Mail list logo
