On 1/26/07, Philip Hallstrom [EMAIL PROTECTED] wrote:
Well,
I use portsnap and portupgrade on a regular basis and therefore I could
watch very often the rebuild of ports - a nice and neat thing of FreeBSD.
Bit sometimes I or someone else installs ports an they install
dependencies and then
Well,
I use portsnap and portupgrade on a regular basis and therefore I could
watch very often the rebuild of ports - a nice and neat thing of FreeBSD.
Bit sometimes I or someone else installs ports an they install
dependencies and then he/she or I decide to kill/delete a specific port,
but very
In response to O. Hartmann [EMAIL PROTECTED]:
Well,
I use portsnap and portupgrade on a regular basis and therefore I could
watch very often the rebuild of ports - a nice and neat thing of FreeBSD.
Bit sometimes I or someone else installs ports an they install
dependencies and then he/she
On 25/01/07, Bill Moran [EMAIL PROTECTED] wrote:
In response to O. Hartmann [EMAIL PROTECTED]:
Well,
I use portsnap and portupgrade on a regular basis and therefore I could
watch very often the rebuild of ports - a nice and neat thing of FreeBSD.
Bit sometimes I or someone else installs
[EMAIL PROTECTED] writes:
Is there a way cleaning up automatically a messy ports collection? Like
portupgrade does, only the opposite way, not rebuilding/reinstalling a
rebuilt/upgraded port, looking for stale ports never used anymore by
another port?
sysutils/pkg_cutleaves
Robert Huff wrote:
I use portupgrade.
I've never used pkg_deinstall, but given that portupgrade gets
... confused ... occasionally I look suspiciously at anything that
promises clean upward recursion.
Many people prefer sysutils/portmanager over portupgrade. As usual, YMMV.
Well,
I use portsnap and portupgrade on a regular basis and therefore I could
watch very often the rebuild of ports - a nice and neat thing of FreeBSD.
Bit sometimes I or someone else installs ports an they install
dependencies and then he/she or I decide to kill/delete a specific port,
but very
