On 2021/02/18 22:29, Christian Weisgerber wrote:
> Stuart Henderson:
> 
> > I think we are getting to the stage where we should just mark them BROKEN
> > with an identifiable tag, so that we don't have to wade through them when
> > identifying other ports breakage in builds.
> > 
> > Then if no updates happen maybe remove them in a few months (say, a bit
> > after 6.9 is done).
> 
> If that approach had been suggested earlier, I wouldn't have spent
> time fixing random ports I have no interest in.

well, me too.

> How about we all give it a big push and fix the remaining ones?

Here are some candidates to "fix" tedu-style...

> > audio/gtkpod                            UPDATE    [email protected]
newer release is still old and has changed quite a lot, so
wants starting from nearly scratch. probably still doesn't support
anything new. main homepage broken.

> > comms/birda                             -         [email protected]
> > comms/jpilot                            -         [email protected]
> > comms/scmxx                             UPDATE    [email protected]
for old mobile phones/portable devices

> > comms/seyon                             -         [email protected]
newer (well, less old) release still not clean

> > editors/beaver                          -         [email protected]
gtk2, no release in years, dropped in other OS packaging

> > editors/tea                             UPDATE    [email protected]
hardcodes -lstdc++


Reply via email to