On Feb 15, 2015, at 15:19, Carlo Tambuatco wrote:
On Sun, Feb 15, 2015 at 2:35 PM, Marko Käning wrote:
Last June Clemens hinted out cut_leaves [1], which you might find
interesting.
[1]
https://lists.macosforge.org/pipermail/macports-users/2014-June/035731.html
That's
Hi Carlo,
On 15 Feb 2015, at 19:25 , Carlo Tambuatco oraclmas...@gmail.com wrote:
$ port list leaves and inactive
Especially because you searched for inactive, it should be okay to delete them.
But even if you omitted inactive you could uninstall everything, yet those ports
might be necessary
On 15 Feb 2015, at 19:46 , Carlo Tambuatco wrote:
So build dependencies are *always* left behind after upgrading all ports
whether they are needed to run ports or not?
Yes, if a dependency is installed, then it stays installed until you uninstall
it.
Seems like macports should have an
Okay, well how about something that automatically marks repeated build
dependencies as requested or some other category distinguishing it as
needed only for builds? Just so they aren't left wondering why you're left
with 502 ports on your system when you only asked for like 20 or 30...
On Sun,
On Sun, Feb 15, 2015 at 1:25 PM, Carlo Tambuatco oraclmas...@gmail.com
wrote:
$ port list leaves and inactive
is it generally okay to uninstall everything that comes up in that list?
I know what leaves are but I'm still afraid there are some sort of hidden
run time dependencies I may not be
On Feb 15, 2015, at 10:25 AM, Carlo Tambuatco oraclmas...@gmail.com wrote:
If I do:
$ port list leaves and inactive
# port list probably doesn't do what you think:
man port | less +/ list
# try these:
port installed leaves
port installed inactive
# you may be interested in port -u
On Sun, Feb 15, 2015 at 2:23 PM, Carlo Tambuatco oraclmas...@gmail.com
wrote:
Just so they aren't left wondering why you're left with 502 ports on your
system when you only asked for like 20 or 30...
That's more likely to be library deps though, and those will get quite
large for some ports.
Last June Clemens hinted out cut_leaves [1], which you might find interesting.
[1] https://lists.macosforge.org/pipermail/macports-users/2014-June/035731.html
___
macports-users mailing list
macports-users@lists.macosforge.org
I thought I did a reply all...oops.
On Sun, Feb 15, 2015 at 1:52 PM, Marko Käning mk-macpo...@techno.ms wrote:
On 15 Feb 2015, at 19:46 , Carlo Tambuatco oraclmas...@gmail.com wrote:
So build dependencies are *always* left behind after upgrading all ports
whether they are needed to run
On Sun, Feb 15, 2015 at 1:54 PM, Carlo Tambuatco oraclmas...@gmail.com
wrote:
Seems like macports should have an option that prunes this stuff after
every upgrade. It should be the port developer's responsibility to mark
what is needed to run their port and have the rest deleted after every
That's interesting...but no mention of it in the man pages.
On Sun, Feb 15, 2015 at 2:35 PM, Marko Käning mk-macpo...@techno.ms wrote:
Last June Clemens hinted out cut_leaves [1], which you might find
interesting.
[1]
11 matches
Mail list logo
