On Sat, Jan 23, 2010 at 10:09 AM, Jasper Frumau jasperfru...@gmail.com
wrote:
On Sat, Jan 23, 2010 at 6:26 AM, Scott Haneda talkli...@newgeo.com
wrote:
Do what Daniel suggested in the beginning of this thread.
First, test with the full path, so run:
Hello,
Did something happen to Etoile because the svn checkout failed:
DEBUG: Found Dependency: receipt exists for tiff
DEBUG: Executing org.macports.main (Etoile)
--- Fetching Etoile
DEBUG: Executing org.macports.fetch (Etoile)
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
DEBUG:
On Jan 22, 2010, at 11:09 PM, Jasper Frumau wrote:
On Sat, Jan 23, 2010 at 6:26 AM, Scott Haneda talkli...@newgeo.com wrote:
Do what Daniel suggested in the beginning of this thread.
First, test with the full path, so run:
/opt/local/lib/python2.4/site-packages/django/bin/django-admin.py
On Sat, Jan 23, 2010 at 12:39 PM, Scott Haneda talkli...@newgeo.com wrote:
On Jan 22, 2010, at 11:09 PM, Jasper Frumau wrote:
I am not sure how the command can not be found, since it was called
implicitly. How about we try a few other things, keeping in mind, I know
nothing about django.
On Jan 22, 2010, at 4:59 PM, Ryan Schmidt wrote:
On Jan 22, 2010, at 18:20, Scott Haneda wrote:
For reasons that are too silly to repeat, I am now sitting on a clean 10.6
updated install, with a new MacPorts, and zero ports installed. I will be
installing all my ports new and clean.
On Jan 23, 2010, at 2:19 AM, Jasper Frumau wrote:
On Sat, Jan 23, 2010 at 12:39 PM, Scott Haneda talkli...@newgeo.com wrote:
On Jan 22, 2010, at 11:09 PM, Jasper Frumau wrote:
Looking over some more notes, it does look as though people are symbolic
linking their Django stuff into some
On Sat, Jan 23, 2010 at 2:24 PM, Scott Haneda talkli...@newgeo.com wrote:
Can you supply the following:
$head -n1 /opt/local/lib/python2.4/site-packages/django/bin/django-admin.py
$ head -n1 /opt/local/lib/python2.4/site-packages/django/bin/django-admin.py
#!/usr/bin/env python
This
On Jan 23, 2010, at 3:55 AM, Jasper Frumau wrote:
On Sat, Jan 23, 2010 at 2:24 PM, Scott Haneda talkli...@newgeo.com wrote:
Can you supply the following:
$head -n1 /opt/local/lib/python2.4/site-packages/django/bin/django-admin.py
$ head -n1
On 2010-01-23, at 1:43 AM, Scott Haneda wrote:
If there is any way to simplify it down for a more common user to understand,
I think that may be helpful.
how about two changes (at * suggest ... **)
**
Original guide 3.2. Port Variants
On Jan 23, 2010, at 00:54, Jim Busser wrote:
Within a portfile, and among its first several lines is a variable
platforms (note plural) in which one or more major platforms like darwin,
X11 are definable. I imagine these define the most basic of potential
compatibilities.
Valid values
On 22 Jan 2010, at 23:28, Mark Hattam wrote:
On 22 Jan 2010, at 23:00, Mark Hattam wrote:
On 22 Jan 2010, at 08:57, Ryan Schmidt wrote:
On Jan 22, 2010, at 02:53, Russell Jones wrote:
Ryan Schmidt wrote:
On Jan 21, 2010, at 10:16, Russell Jones wrote:
I filed a bug in trac
On Jan 23, 2010, at 04:21, Scott Haneda wrote:
I am still not understanding this. I add multiple values to build_arch and
uncomment it?
#build_arch i386
-- would become --
build_archx86_64 i386
No. build_arch can only contain a single value.
It's very simple:
On Jan 23, 2010, at 02:43, Frank J. R. Hanstick wrote:
Did something happen to Etoile because the svn checkout failed:
http://trac.macports.org/ticket/20776
___
macports-users mailing list
macports-users@lists.macosforge.org
On 2010-01-23, at 1:43 AM, Scott Haneda wrote:
At the same time, users are not concerned much with this
What you say would be true anytime a simple port install x worked. When
however port install x did not work, it is exceedingly difficult for any user
(who only wants to enjoy some free
On Jan 22, 2010, at 10:01, Andrea Parmgiani wrote:
Did you follow the instructions at
http://trac.macports.org/wiki/Migration?
Yes I did.
Maybe something that I didn't get with this point:
Browse myports.txt and install the ports that you actually want to use (as
opposed to
On Jan 23, 2010, at 15:46, Jim Busser wrote:
On 2010-01-23, at 1:43 AM, Scott Haneda wrote:
At the same time, users are not concerned much with this
What you say would be true anytime a simple port install x worked. When
however port install x did not work, it is exceedingly difficult
On Jan 23, 2010, at 10:46 PM, Ryan Schmidt wrote:
On Jan 22, 2010, at 10:01, Andrea Parmgiani wrote:
Did you follow the instructions at
http://trac.macports.org/wiki/Migration?
Yes I did.
Maybe something that I didn't get with this point:
Browse myports.txt and install the ports
On Jan 23, 2010, at 1:51 PM, Ryan Schmidt ryandes...@macports.org
wrote:
I advocated putting +universal in variants.conf on Snow Leopard and
up. But then I tried it out myself and found too many ports that
fail when built universal for x86_64/i386. Therefore I cannot
advocate this change
On Jan 23, 2010, at 16:49, Scott Haneda wrote:
On Jan 23, 2010, at 1:51 PM, Ryan Schmidt wrote:
I advocated putting +universal in variants.conf on Snow Leopard and up. But
then I tried it out myself and found too many ports that fail when built
universal for x86_64/i386. Therefore I
Good commentary, comments below:
On Jan 23, 2010, at 1:46 PM, Jim Busser jbus...@interchange.ubc.ca
wrote:
On 2010-01-23, at 1:43 AM, Scott Haneda wrote:
At the same time, users are not concerned much with this
What you say would be true anytime a simple port install x worked.
When
On Jan 23, 2010, at 3:31 PM, Ryan Schmidt wrote:
On Jan 23, 2010, at 17:13, Scott Haneda wrote:
Store www files outside of prefix, or leave them in htdocs, or prefix/www/me
?
I think this go around I'm keeping my personal data in ~. wanted to hear
others methods.
Either way.
On Jan 23, 2010, at 4:15 PM, Ryan Schmidt wrote:
The rest makes sense.
What is the harm if you do not remove receipt packages? I was building out
some local stuff with Apple's Package Maker, using it as a glorified way to
put shell scripts and a launchd item where I wanted it. I ended
On Jan 23, 2010, at 19:47, Jim Busser wrote:
On 2010-01-23, at 1:51 PM, Ryan Schmidt wrote:
postgresql84 does not currently build correctly universal for x86_64/i386:
http://trac.macports.org/ticket/21358
As postgresql84 does not currently build correctly universal for x86_64/i386
Hello,
I installed dot2tex with 'sudo port install dot2tex', but it does not
set the path in my ~/.profile. The executable python script is in
/opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/dot2tex
Is it supposed to be left there after installation, without a link
from
In trying to build purely i386 on a MacBook Core 2 Duo (Snow Leopard)
I set
build_arch i386
I reset back to commented-out
variants.conf (+universal)
? did I need to alter in macports.conf:
universal_archs x86_64 i386
problem seems in
--- Building ossp-uuid
25 matches
Mail list logo
