polling opinions: how much QT3/KDE3.5 to preserve in dports this July?
dragonflybsd at marino.st
Sun Jun 30 02:46:57 PDT 2013
On 6/28/2013 03:09, Justin Sherrill wrote:
> Delete with abandon! If you're going to end up maintaining it
> (likely), and you really don't want to do it (sounds likely), don't.
> The amount of time you spend on dports having the rest of the
> collection run is far more valuable to all users than to a subset that
> doesn't want to upgrade KDE (ignoring any arguments about KDE3 being
> more useful than KDE4, which I am not interested in.)
> Ports and pkgsrc management burns people out over time because they're
> trying to maintain software they have no personal utility for; I've
> seen it happen multiple times. If something doesn't seem worth the
> effort to you, cut it out, and others who need it, whatever it is, can
> step in.
This may be an acceptable compromise:
Carry the ports until the DragonFly 3.6 Release tag (for dports). That
way DragonFly 3.6 RELEASE repository will have them, but the DragonFly
3.6 LATEST branch won't after the first update.
Depending on when FreeBSD actually deletes the ports, this may be easy
to do. I suspect that it will take a while to actually purge 250+ ports
and that it won't get done tomorrow or maybe even in a month or two.
More information about the Users