On 2019-07-18 11:12, Kristian Fiskerstrand wrote: > Should we be more specific as to how not to enable it here? is it a > USE-flag? does it require a package mask for newer versions if it is > always used for the newer ones?
Good point, this should explicitly say "do not emerge new versions". My own thoughts on the matter have been that since we are now in the process of stabilising syncthing-1.1.4 (i.e. the latest version which does not force the use of large blocks) and that I do not intend to push the 1.2.0 ebuild until stabilisation has been concluded, it would be up to individual users to mask newer versions should they insist on using ~arch ebuilds. > Also cluster immediately made me think of server<>client relationship > and this only affecting server side, which probably doesn't fit well > with syncthing, but admittedly I don't use it so not familiar with the > nomenclature. I guess it is a bit subjective and/or based on one's experience, in my case "cluster" brings to mind a cluster of peers. Anyway, this is the wording from the official upstream statement so I would rather not change it unless there is a good reason for it - like the Gentoo-specific clarification you have suggested above. PS. For the record, I have already published this news item (a couple of hours ahead of schedule I am afraid, I didn't remember the exact time I submitted the RFC) so I'll include your comments in the second revision. -- MS
