Gkrellm not building

[Amit Sengupta]

Ok, got that. I am just hoping I wont have to build a whole lot of ports
again due to a change in gtk/gtk2. Thanks for the info.

Amit

On Sat, Sep 22, 2018 at 8:54 AM Kevin Oberman <rkoberman at gmail.com> wrote:

> On Fri, Sep 21, 2018 at 6:58 AM Amit Sengupta <sengupta.amit at gmail.com>
> wrote:
>
>> Awesome. Thanks a lot Adam. Will follow your advice.
>>
>> On Fri, 21 Sep 2018 at 19:24, Adam Weinberger <adamw at adamw.org> wrote:
>>
>> > On Fri, Sep 21, 2018 at 7:47 AM Amit Sengupta <sengupta.amit at gmail.com>
>> > wrote:
>> > >
>> > > Thanks a lot Adam . I do run portsnap fetch update every morning so I
>> > guess my ports are up to date. I had no idea gkrellm had become gkrellm2
>> > because I have been using  gkrellm for many years and only recently
>> decided
>> > to update it.  Is there something which I should do to know that a port
>> has
>> > changed names? I couldnt find anything in UPDATING but as you said the
>> > switch happened a long time back it wouldnt make sense to check
>> UPDATING.
>> >
>> > Something isn't right with portsnap on your machine, because those
>> > gkrellm port files shouldn't even be on your system anymore (portsnap
>> > should have deleted them). You might try deleting your ports tree and
>> > re-extracting the snapshot (portsnap fetch extract).
>> >
>> > Removed files only get an annotation in /usr/port/MOVED, but that file
>> > isn't very end-user-friendly.
>> >
>> > # Adam
>>
>>
> I will mention that the main difference between gkrellm and gkrellm2 is
> the move from gtk to gtk2. That may require installing a port or two, but
> you may be ale to remove gtk and, perhaps, a few other old ports. Not much
> left that uses gtk.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman at gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>