Bryan Blackburn wrote:
On Apr 17, 2007, at 3:04 AM, Bernard Desgraupes wrote:
Just out of curiosity, I've been poking my nose in the various Tcl
packages which implement the port command and the following
condition found at the end of darwinports_fastload.tcl (in /Library/
Tcl/darwinport
On Apr 17, 2007, at 3:04 AM, Bernard Desgraupes wrote:
Just out of curiosity, I've been poking my nose in the various Tcl
packages which implement the port command and the following
condition found at the end of darwinports_fastload.tcl (in /Library/
Tcl/darwinports1.0) strikes me as very od
There are several versions of X11 for OSX -- the one Apple distributes,
and in macports, xfree86 and xorg, both in several variants. Could
someone give us a summary of the state of X11 on OSX? What should be
used when? Where are we headed?
I'm so far not able to start the XFree86 version I install
James Berry wrote:
>
> The port author was calling exit, on i386, whenever the
> Portfile was opened.
> I've checked in a revision to that port (r24159) which defers the
> error report until build time, and then does so in a somewhat nicer
> fashion.
Thanks! In my book, port is already much nicer
On Apr 17, 2007, at 8:55 PM, Greg Shenaut wrote:
On Apr 17, 2007, at 8:33 PM, James Berry wrote:
Hi Greg,
What Mac OS X system version are you running? And have you
installed the latest xcode?
10.4.9 PPC, XCODE 2.4
Greg. Hmm. I haven't seen any issues with that sha1 code in
practical
On Apr 17, 2007, at 7:27 PM, David Liontooth wrote:
I believe that if you pass the -p flag to port, that this error (and
any others) in a particular port will be ignored. The -p flag
basically says that, while processing multiple ports (such as those
furnished by all) that an error in one shoul
On Apr 17, 2007, at 8:33 PM, James Berry wrote:
Hi Greg,
What Mac OS X system version are you running? And have you
installed the latest xcode?
10.4.9 PPC, XCODE 2.4
Greg
James
On Apr 17, 2007, at 8:29 PM, Greg Shenaut wrote:
On Apr 17, 2007, at 6:44 PM, James Berry wrote:
Hi Greg
Hi Greg,
What Mac OS X system version are you running? And have you installed
the latest xcode?
James
On Apr 17, 2007, at 8:29 PM, Greg Shenaut wrote:
On Apr 17, 2007, at 6:44 PM, James Berry wrote:
Hi Greg,
You have darwinports 1.101 installed? We hoped we'd left all those
users beh
On Apr 17, 2007, at 6:44 PM, James Berry wrote:
Hi Greg,
You have darwinports 1.101 installed? We hoped we'd left all those
users behind (or better, that they'd all upgraded by now).
Support for upgrades from 1.1 was lost sometime around 1.4. Your
best bet will be to re-install from the
On Apr 17, 2007, at 8:59 PM, Didier Arenzana wrote:
Hi,
I believe "sudo -i" does exactly the same as a "sudo su -".
Regards,
Didier.
Close, but there's still a difference:
$sudo -i
#env
SHELL=/bin/sh
TERM=screen
USER=root
SUDO_USER=pipping
SUDO_UID=501
PATH=/bin:/sbin:/usr/bi
James Berry wrote:
> Hi David,
>
> On Apr 17, 2007, at 9:47 AM, David Liontooth wrote:
>
>> Emmanuel Hainry wrote:
>>> Citando Ryan Schmidt :
>>>
Perhaps you meant to clean only the *installed* ports. But I'm still
not clear why. I think MacPorts automatically cleans each port after
Hi Greg,
You have darwinports 1.101 installed? We hoped we'd left all those
users behind (or better, that they'd all upgraded by now).
Support for upgrades from 1.1 was lost sometime around 1.4. Your best
bet will be to re-install from the MacPorts 1.4 disk image available
at http://trac
What does this message mean? (And what do I need to do about it?)
% sudo port selfupdate
DarwinPorts base version 1.101 installed
Selfupdate failed: couldn't open "/opt/local/var/db/dports/sources/
rsync.rsync.opendarwin.org_dpupdate1/base/dp_version": no such file
or directory
Greg Shenaut
The MacPorts team is very proud to announce our third release of
MacPorts within several days.
The pace of change has been fast and furious. This time we're just
furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove
remnants of
launchd
Hi David,
On Apr 17, 2007, at 9:47 AM, David Liontooth wrote:
Emmanuel Hainry wrote:
Citando Ryan Schmidt :
Perhaps you meant to clean only the *installed* ports. But I'm still
not clear why. I think MacPorts automatically cleans each port after
it's installed, so you really shouldn't need t
For some reason man isn't searching the paths in man.conf (even tried
man -C). Something I've installed at some point must have changed
this, still not sure where it is looking for MANPATHs. I was able to
fix the issue by adding an export for MANPATH in my .profile. This
will work better
I can't run "port selfupdate" on a fresh install of 1.4. It fails
when building Pextlib, complaining about socket.h.
Anyone have a clue? I've searched the list archives and found
nothing similar.
Thanks in advance,
-d
===> making all in src/pextlib1.0
gcc -c -DUSE_TCL_STUBS -g -O2 -W -W
2007/4/17, Elias Pipping <[EMAIL PROTECTED]>:
On Apr 16, 2007, at 11:14 PM, Ryan Schmidt wrote:
> A bit unrelated to your question, but: I've
> seen others use "sudo su -" but I haven't
> understood it. Why not use "sudo -s"? Isn't
> that equivalent?
In addition to what Landon said, you might a
Thanks, it works now. I had to update Emacs.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Hezekiah Barnes wrote:
> It appears I'm missing almost all my manual pages for my ports
> including the port man page itself. Anyone see this & know how to fix
> it. The paths are correct in man.conf but the manual pages seem to
> have disappeared. Only thing I've done recently was to upgrade to
Emmanuel Hainry wrote:
> Citando Ryan Schmidt :
>
>> Perhaps you meant to clean only the *installed* ports. But I'm still
>> not clear why. I think MacPorts automatically cleans each port after
>> it's installed, so you really shouldn't need to clean the installed
>> ports.
>>
>
> port auto
It appears I'm missing almost all my manual pages for my ports
including the port man page itself. Anyone see this & know how to
fix it. The paths are correct in man.conf but the manual pages seem
to have disappeared. Only thing I've done recently was to upgrade to
1.40 & recently 1.42
On Apr 17, 2007, at 6:13 PM, Watson Ladd wrote:
I have the following problem:
$sudo port uninstall category:gnome and installed
results in complaints about gnome-vfs depending on gconf. Is there
a way
to tell macports to do things in dependency order?
No, I don't think so.
Anyway,
sudo
I have the following problem:
$sudo port uninstall category:gnome and installed
results in complaints about gnome-vfs depending on gconf. Is there a way
to tell macports to do things in dependency order?
Thanks,
Watson Ladd
signature.asc
Description: OpenPGP digital signature
_
for some reason py-pytz's portfile is in python/py-tz
this is most likely not intended.
Regards,
Elias Pipping
On Apr 17, 2007, at 12:14 PM, Jochen Küpper wrote:
Hi,
I repeatedly get messages about py-tz not found, i.e.
sudo port upgrade active
Password:
Error: No port py-tz found.
I am
On Apr 17, 2007, at 04:24, Emmanuel Hainry wrote:
Citando Ryan Schmidt :
Perhaps you meant to clean only the *installed* ports. But I'm still
not clear why. I think MacPorts automatically cleans each port after
it's installed, so you really shouldn't need to clean the installed
ports.
port a
Hi,
I repeatedly get messages about py-tz not found, i.e.
sudo port upgrade active
Password:
Error: No port py-tz found.
I am at MacPorts-1.4.2 and the port is actually called py-pytz now.
The only file I could find py-tz mentioned in is /opt/local/var/db/
dports//sources/rsync.rsync.darwinpo
In article <[EMAIL PROTECTED]>,
James Berry <[EMAIL PROTECTED]> wrote:
> Hi Dave,
>
> On Apr 16, 2007, at 2:57 PM, Dave Hill wrote:
>
> > In article
> > > g>,
> > James Berry <[EMAIL PROTECTED]> wrote:
> >
> >> MacPorts 1.4.1 has been released for selfupdate. It should hit the
> >> rsync ser
On Apr 17, 2007, at 6:37 PM, [EMAIL PROTECTED] wrote:
Hi everyone,
I was updating some outdated ports:
The following installed ports are outdated:
gnuplot4.0.0_3 < 4.0.0_4
[...]
The new gnuplot fails to build. Can anyone help me interpret this
error?
Thanks.
Hel
Hi everyone,
I was updating some outdated ports:
The following installed ports are outdated:
gnuplot4.0.0_3 < 4.0.0_4
[...]
The new gnuplot fails to build. Can anyone help me interpret this error?
Thanks.
-8<--
Citando Ryan Schmidt :
>
> Perhaps you meant to clean only the *installed* ports. But I'm still
> not clear why. I think MacPorts automatically cleans each port after
> it's installed, so you really shouldn't need to clean the installed
> ports.
port automatically cleans the work (build) director
Just out of curiosity, I've been poking my nose in the various Tcl
packages which implement the port command and the following condition
found at the end of darwinports_fastload.tcl (in
/Library/Tcl/darwinports1.0) strikes me as very odd
if { "/usr/lib/sqlite3" != "" } {
set dir "/usr/lib/sq
On Apr 17, 2007, at 00:05, David Liontooth wrote:
$ sudo port selfupdate
DarwinPorts base version 1.400 installed
Downloaded MacPorts base version 1.420
Configuring, Building and Installing new MacPorts base
selfupdate done!
Great! You got MacPorts 1.4.2.
$ sudo port -f clean --all all
--->
Hi Teus,
On 17/04/2007, at 17:05, Teus Benschop wrote:
Here is a request for the person(s) who are adding or removing ports.
The gtk26 port was originally brought in because the gtk2 port
wasn't performing so well in certain areas. But these days the gtk2
port is working well, and there is
Here is a request for the person(s) who are adding or removing ports.
The gtk26 port was originally brought in because the gtk2 port wasn't
performing so well in certain areas. But these days the gtk2 port is
working well, and there is no need anymore for the gtk26 port.
Is it possible to rem
35 matches
Mail list logo
