If direct mode is removed, I will use the following to work around:
port destroot foo
rsync -tpogHlr /opt/local/var/macports/build/foo/work/destroot/opt/local /opt
[or wherever the destroot is]
This would effectively turn macports into a simple way to build packages
based on the maintainer's hav
On 24 Jan 2009, at 03:46, Rainer Müller wrote:
Bryan Blackburn wrote:
Personally, I'd like to see direct mode deprecated, and when 10.3
support is
officially dropped, it can be removed entirely. Other than the old
performance issues with the large number of hardlinks, I don't see
any
adva
Bryan Blackburn wrote:
> Personally, I'd like to see direct mode deprecated, and when 10.3 support is
> officially dropped, it can be removed entirely. Other than the old
> performance issues with the large number of hardlinks, I don't see any
> advantage to using direct over image mode. Are ther
On Fri, Jan 23, 2009 at 04:39:54PM -0500, Daniel J. Luke said:
> On Jan 23, 2009, at 4:15 PM, Bryan Blackburn wrote:
>>> For the list archives, this was fixed (in 10.4, IIRC).
>>
>> Personally, I'd like to see direct mode deprecated, and when 10.3
>> support is
>> officially dropped, it can be re
On Jan 23, 2009, at 4:15 PM, Bryan Blackburn wrote:
For the list archives, this was fixed (in 10.4, IIRC).
Personally, I'd like to see direct mode deprecated, and when 10.3
support is
officially dropped, it can be removed entirely. Other than the old
performance issues with the large number
On Fri, Jan 23, 2009 at 09:34:09AM -0500, Daniel J. Luke said:
> On Jan 23, 2009, at 8:35 AM, robert delius royar wrote:
>>> Direct mode is certainly less well tested than image mode. I've never
>>> used it. Is there a particular reason why you are using it?
>>
>> I began using Darwinports very so
On Jan 23, 2009, at 8:35 AM, robert delius royar wrote:
Direct mode is certainly less well tested than image mode. I've
never used it. Is there a particular reason why you are using it?
I began using Darwinports very soon after DP was created. When
Image mode was added, a few of us (perhaps
Fri, 23 Jan 2009 (06:27 -0600 UTC) Ryan Schmidt wrote:
On Jan 19, 2009, at 07:37, robert delius royar wrote:
So much traffic on this thread, so much time spent answering questions. But
I do not recall any of the answerers trying
port provides /opt/local/lib/libintl.dylib
Sorry; I thought it
Ryan Schmidt wrote:
> "Actually it surprises me that MacPorts base is shelling out to an ln
> command at all; why aren't we using the [file link] Tcl command?"
What seems even stranger to me is that it's the *de*activate phase
that's failing, which appears to only use 'file delete'.
- Josh
__
On Jan 19, 2009, at 07:37, robert delius royar wrote:
So much traffic on this thread, so much time spent answering
questions. But I do not recall any of the answerers trying
port provides /opt/local/lib/libintl.dylib
Sorry; I thought it was already understood that libintl is the
internatio
On Sun, Jan 18, 2009 at 10:04 PM, Ryan Schmidt wrote:
> On Jan 18, 2009, at 20:50, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt wrote:
>>>
>>
>>> Try:
>>>
>>> sudo port install gettext
>>
>> Thanks...that worked.
>
> Great!
>
>> Should I now try to update with 'sudo port u
So much traffic on this thread, so much time spent answering questions.
But I do not recall any of the answerers trying
port provides /opt/local/lib/libintl.dylib
That would have pointerd out that the initial problem of gettext wanting
to reinstall itself (perhaps for no good reason) had remove
On Sun, Jan 18, 2009 at 08:01:57PM -0600, Ryan Schmidt said:
[...]
>
> We should also consider forcing MacPorts base to always use vital
> utilities like ln and touch via their absolute paths in /bin or /usr/bin
> and not allow a MacPorts version to interfere. We might consider the same
> for t
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt wrote:
>
> On Jan 18, 2009, at 20:39, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
>>
>>> On Jan 18, 2009, at 20:18, Doctor Who wrote:
>>>
Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mes
On Sun, Jan 18, 2009 at 9:57 PM, Ryan Schmidt wrote:
>
> On Jan 18, 2009, at 20:53, Doctor Who wrote:
>
>> Also, does removing coreutils cause a problems with paths for tools
>> like 'ls' now? How do I fix the paths so I can use the tools again?
>>
>> tbook:~ who$ ls
>> -bash: /opt/local/bin/ls:
On Jan 18, 2009, at 20:50, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt wrote:
Try:
sudo port install gettext
Thanks...that worked.
Great!
Should I now try to update with 'sudo port upgrade outdated'?
Sure, go ahead. I know there have been a lot of X11/xorg-rela
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt wrote:
>
> On Jan 18, 2009, at 20:39, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
>>
>>> On Jan 18, 2009, at 20:18, Doctor Who wrote:
>>>
Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mes
On Jan 18, 2009, at 20:53, Doctor Who wrote:
Also, does removing coreutils cause a problems with paths for tools
like 'ls' now? How do I fix the paths so I can use the tools again?
tbook:~ who$ ls
-bash: /opt/local/bin/ls: No such file or directory
Since /opt/local/bin/ls doesn't exist, the
On Jan 18, 2009, at 20:39, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
On Jan 18, 2009, at 20:18, Doctor Who wrote:
Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mess my system up more. Would you please outline the steps I should
take one b
On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
> On Jan 18, 2009, at 20:18, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:
>>
>>> On Jan 18, 2009, at 19:10, Rainer Müller wrote:
>>>
Doctor Who wrote:
> Well, I hope there is some way to fix/recover f
On Jan 18, 2009, at 20:18, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:
On Jan 18, 2009, at 19:10, Rainer Müller wrote:
Doctor Who wrote:
Well, I hope there is some way to fix/recover from this. I cannot
even list files on my file system in Terminal.app (as evide
On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:
> On Jan 18, 2009, at 19:10, Rainer Müller wrote:
>
>> Doctor Who wrote:
>>
>>> Well, I hope there is some way to fix/recover from this. I cannot
>>> even list files on my file system in Terminal.app (as evidenced by the
>>> attempt at the ls c
On Jan 18, 2009, at 19:10, Rainer Müller wrote:
Doctor Who wrote:
Well, I hope there is some way to fix/recover from this. I cannot
even list files on my file system in Terminal.app (as evidenced by
the
attempt at the ls command above).
It is trying to use /opt/local/bin/ls which is brok
On Sun, Jan 18, 2009 at 8:10 PM, Rainer Müller wrote:
> Doctor Who wrote:
>> On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn wrote:
>>> On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
Doctor Who wrote:
> I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and ha
Doctor Who wrote:
> On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn wrote:
>> On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
>>> Doctor Who wrote:
I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
5 or 6 ports that needed updating. I then ran a 'sudo
On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn wrote:
> On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
>> Doctor Who wrote:
>> > I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
>> > 5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
>> > out
On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
> Doctor Who wrote:
> > I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
> > 5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
> > outdated' and it failed after a while with errors like:
> >
> > s
On Sun, Jan 18, 2009 at 6:46 PM, Rainer Müller wrote:
> Doctor Who wrote:
>> I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
>> 5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
>> outdated' and it failed after a while with errors like:
>>
>> sudo port upgr
Doctor Who wrote:
> I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
> 5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
> outdated' and it failed after a while with errors like:
>
> sudo port upgrade outdated
> ---> Deactivating gettext @0.17_3
> Error: De
29 matches
Mail list logo
