Well, I don't really know what happened, and my primary concern at the time was
to get things working again ... without much inspiration to try and break them
anew to understannd exactly what went awry. I know that doesn't help much ...
I should add that I've removed a good deal of the docs that
There's another option for you that might save you diskspace in return for
time. I've noticed that MacPorts ports tend to depend on the full set of
dependencies a given project could have, ffmpeg being a good example. They also
tend to install things you probably already have installed, like X11
Thank you Sterling, Ryan, Lawrence, Chris - I have followed your
suggestions, moving the whole of the macports build tree and changing
portdbpath as suggested by Lawrence, then cleaning up inactive
installs as suggested by Chris and Ryan (I hit minor problems with
py2x-distribute in a few cases, ha
On Aug 15, 2013, at 09:25, René J.V. Bertin wrote:
> If only I knew ... It's possible that I did an "-u uninstall inactive", I
> have a vague memory that I should never use -u again!
"-u" has two different and IMHO unrelated uses in MacPorts.
The one I find useful is in connection with "upgrade
On Aug 15, 2013, at 16:09, Daniel J. Luke wrote:
> On Aug 15, 2013, at 9:22 AM, Arno Hautala wrote:
>> On Thu, Aug 15, 2013 at 9:16 AM, Ryan Schmidt
>> wrote:
>>>
>>> If you want to combine those two operations into a single command, it's:
>>>
>>> sudo port -u upgrade outdated
>>
>> Ah, goo
On Aug 15, 2013, at 9:22 AM, Arno Hautala wrote:
> On Thu, Aug 15, 2013 at 9:16 AM, Ryan Schmidt wrote:
>>
>> If you want to combine those two operations into a single command, it's:
>>
>> sudo port -u upgrade outdated
>
> Ah, good point. I don't recall why I had them split out like that.
> Re
On Thu, Aug 15, 2013 at 9:16 AM, Ryan Schmidt wrote:
>
> If you want to combine those two operations into a single command, it's:
>
> sudo port -u upgrade outdated
Ah, good point. I don't recall why I had them split out like that.
Restricting commands to single actions? Ignorance? I don't know.
On Aug 15, 2013, at 08:05, Arno Hautala wrote:
> It's not exactly what you're looking for, but you could run: port
> uninstall inactive and actinact
>
> "actinact" is only those ports that have an active version as well as
> an inactive version. Combining it with "inactive" means install any
> i
On Aug 15, 2013, at 07:59, René J.V. Bertin wrote:
> On Aug 15, 2013, at 10:33, Chris Jones wrote:
>
>> port uninstall inactive
>
>
> I tried that once, and had to restore my whole installation tree from backup.
That shouldn't have been necessary. What went wrong?
> I would be great if one
On Thu, Aug 15, 2013 at 8:59 AM, "René J.V. Bertin" wrote:
>
> On Aug 15, 2013, at 10:33, Chris Jones wrote:
>>
>> port uninstall inactive
>
> I tried that once, and had to restore my whole installation tree from backup.
> I would be great if one could uninstall all old versions except for the
>
On Aug 15, 2013, at 10:33, Chris Jones wrote:
>
> port uninstall inactive
I tried that once, and had to restore my whole installation tree from backup.
I would be great if one could uninstall all old versions except for the
previous version!
___
ma
Hi,
On Thu, Aug 15, 2013 at 02:22:22AM -0400, Lawrence Velázquez wrote:
> This will not work under MacPorts 2.2.0, and it's not clear that this
> will be fixed.
jmr might not be doing it, but I will definitely fix this, one way or
another; either by normalizing portdbpath after reading it from th
Hi,
"port list" doesn't do what you think it does:
https://trac.macports.org/wiki/FAQ#portlist
You want "port installed inactive" instead.
yeah, I knew that, my mistake... Its just 'port list' makes such sense
grammatically, it slips out sometimes. Guess that is why its in the FAQ
as other
On Aug 15, 2013, at 03:33, Chris Jones wrote:
> Before you start messing around like this, have you first made sure you don't
> have a lot of unwanted stuff lying around you don't need.
>
> sudo port list inactive
>
> will show packages updated, but not active. Usually the result of an update,
Hi,
Before you start messing around like this, have you first made sure you
don't have a lot of unwanted stuff lying around you don't need.
sudo port list inactive
will show packages updated, but not active. Usually the result of an
update, which doesn't completely remove the old versions. Y
On Aug 14, 2013, at 10:21 PM, Bob M wrote:
> I have an MB air with internal (smallish) SSD. I need some of the programs
> provided by MacPorts at all times, but I'm happy to do all builds while
> connected to a large-ish external HD. I just hit a crisis when the /opt
> directories hit 27GB. So
On Aug 14, 2013, at 21:21, Bob M wrote:
> Hi all; I have an MB air with internal (smallish) SSD. I need some of
> the programs provided by MacPorts at all times, but I'm happy to do
> all builds while connected to a large-ish external HD. I just hit a
> crisis when the /opt directories hit 27GB.
Bob,
You could use the command
port contents
to see which files your desired port(s) really install (and presumably are
needed for those desired ports to function).
-Sterling
On Aug 14, 2013, at 7:21PM, Bob M wrote:
> Hi all; I have an MB air with internal (smallish) SSD. I need some of
> t
Hi all; I have an MB air with internal (smallish) SSD. I need some of
the programs provided by MacPorts at all times, but I'm happy to do
all builds while connected to a large-ish external HD. I just hit a
crisis when the /opt directories hit 27GB. So what I want to do is to
put as much as possible
19 matches
Mail list logo
