svn commit: r534093 - in head: . audio audio/festvox-czech audio/gkrellmvolume2 audio/mixmos audio/mma audio/pd-cyclone audio/shorten audio/taglib-sharp audio/xhippo biology biology/consed biology/...

[Baptiste Daroussin]

On Thu, May 07, 2020 at 09:29:56AM +0200, Ulrich Spörlein wrote:
> Am Mi., 6. Mai 2020 um 10:37 Uhr schrieb Antoine Brodin <antoine at freebsd.org>:
> > Trying build of xvattr-1.3_10 even though it is marked BROKEN.
> > ===>   xvattr-1.3_10 depends on file: /usr/local/sbin/pkg - found
> > => xvattr_1.3.orig.tar.gz doesn't seem to exist in
> > /poudriere/ports/custom1/distfiles/.
> > => Attempting to fetch
> > http://xvattr.sourcearchive.com/downloads/1.3/xvattr_1.3.orig.tar.gz
> > fetch: http://xvattr.sourcearchive.com/downloads/1.3/xvattr_1.3.orig.tar.gz:
> > Not Found
> > => Couldn't fetch it - please try to retrieve this
> > => port manually into /poudriere/ports/custom1/distfiles/ and try again.
> > *** Error code 1
> >
> > Stop.
> > make: stopped in /poudriere/ports/custom1/x11/xvattr
> >
> >
> > Antoine
> 
> Thanks for having another look. Of course, I already have those
> distfiles so the ports continue to build fine for me. I haven't
> actually _run_ esniper in forever, so I wasn't aware of the runtime
> breakage.
> 
> Overall, this mass deletion looks like we're optimizing developer
> convenience over our users convenience :/

I do disagree here: user experience is bad when we cannot build the actual port.

When the ports is marked as broken, the regular users cannot already use them.
We keep the ports as broken for 6 month before deletion, so anyone willing to
fix them has more than time to do it. After those 6 month we are deleting them.
Which means they have already been put out of the scope of the actual final
users for at least 6 month (plus the time it has been unnoticed as broken before
being marked as broken).

So for end users: being broken, being marked as broken and being removed from
the ports results in the same situation: there is no binary package at all. The
first being the worst because he may try to build and end up in a broken
situation.

For the developers, being marked as broken help noting the port is actually
broken. (I know portsmon is dead and so there is no automatic notification in
case something is marked as broken, but this can be fixed by using services
provided by freshports and/or phabricator).
6 month broken, the dev has more then plenty of time to fix it.
After those 6 month the developer can still resurect the port easily (we are
using a VCS it is not as if it was destroyed forever).

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20200507/cb781311/attachment.sig>