portmaster [was: New /bin/sh based script to manage ports]

[Hans Lambermont]

David J. Weller-Fahy wrote:
> David J. Weller-Fahy wrote:
>> Hrm... would something like the attached script be sufficient?  it
>> outputs a tree-like view of what will be updated.  It's not very
>> complex, and doesn't take into account things like removing ports
>> already ouput from any future output, but it works for me.
> 
> Which apparently didn't get through, here's an inline version:
...

Nice work ! The output grows very quicky with the missing hash-like
filter. Here's a snippet of the well over 1000 lines of output I get :

:::::::::::>pkgconfig-0.17.2::pkgconfig-0.20
:::::::::::::>gettext-0.14.5::gettext-0.14.5_1
::::::::::::::>libtool-1.5.20::libtool-1.5.22_1
:::::::::::::::>libtool-1.5.20::libtool-1.5.22_1
:::::::::::::>libtool-1.5.20::libtool-1.5.22_1
::::::::::::::>libtool-1.5.20::libtool-1.5.22_1
::::::::::::>libtool-1.5.20::libtool-1.5.22_1
::::::::::::>gettext-0.14.5::gettext-0.14.5_1

Is there a way to implement a perl-like hash filter in sh land to clean
this up ?

As a next step to such a filter I would suggest to reverse the
dependency output, so that the build order gets shown.

What do you think of this ?

regards,
   Hans Lambermont