Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Oct 2019 23:07:42 -0400
From:      "Mikhail T." <mi+thun@aldan.algebra.com>
To:        Tobias Kortkamp <tobik@freebsd.org>, Gleb Popov <arrowd@freebsd.org>
Cc:        ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r513679 - head/sysutils/fusefs-smbnetfs/files
Message-ID:  <f26493f6-8ba8-c926-0402-f76b3d55926a@aldan.algebra.com>
In-Reply-To: <20191006081114.GA33887@urd.tobik.me>
References:  <201910031745.x93Hje5x059120@repo.freebsd.org> <20191006054444.GB62549@urd.tobik.me> <CALH631=WA=D2gRWG4t72CMr4Z%2BOt5303ZV-1ng0uQ0ZiRGs1WA@mail.gmail.com> <20191006081114.GA33887@urd.tobik.me>

next in thread | previous in thread | raw e-mail | index | archive | help
On 06.10.19 04:11, Tobias Kortkamp wrote:
> We do not have options specific PORTREVISIONs and there are more 
> package repositories than pkg.FreeBSD.org. If you have previously 
> built your packages with LIBSECRET=on, the applied fix will change the 
> package in a non-trivial way. However since PORTREVISION was not 
> bumped Poudriere or other package builders will not rebuild the 
> package. Bascially people will have to micromanage/force the rebuild 
> fusefs-smbnetfs if they want this fix. fusefs-smbnetfs is hardly an 
> expensive package to build so saving rebuilds at the cost of wasting 
> people's time is not worth it and bad UX.

What I'm trying to avoid is the opposite -- thousands of 
package-builders, tens of thousands of users, rebuilding their 
fusefs-smbnetfs for no reason whatsoever. /That/ is bad user experience...

Considering, that no one has contacted me about adding this particular 
patch -- despite it being available on SourceForge for months -- I 
suspect rather strongly, that it simply is not used with LIBSECRET by 
anyone... Or, if a few people are actually building it with the option 
turned on, that's a deliberate action and they are not trying to disable 
the feature through configuration -- which disabling is now fixed by the 
new patch.

Yours,

    -mi




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f26493f6-8ba8-c926-0402-f76b3d55926a>