* Chris Suszynski [11/07/2024 11:16] :
>
> What's the reason for treating Go differently than other languages?
> Fedora does not patch out calls to sites like npmjs.com, pypi.org,
> rubygems.org or repo.maven.apache.org, doesn't it?
Actually, we do.
https://src.fedoraproject.org/rpms/perl-Dancer2
On 11/07/2024 13:16, Chris Suszynski wrote:
Fedora does not patch out calls to sites
vcpkg package has telemetry disabled by default.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
--
___
devel mailing list -- devel@lists.fedoraproject.org
T
Personally I agree with maxwells stance fedora is a privacy friendly distro.
On Fri, 12 Jul 2024 at 12:03, Ralf Corsépius wrote:
>
>
> Am 11.07.24 um 1:16 PM schrieb Chris Suszynski:
> >> I support keeping the Google Go module proxy disabled by default. Our
> packages should not send telemetry d
Am 11.07.24 um 1:16 PM schrieb Chris Suszynski:
I support keeping the Google Go module proxy disabled by default. Our packages
should not send telemetry data to Google without explicit opt-in.
What's the reason for treating Go differently than other languages? Fedora does
not patch out call
> I support keeping the Google Go module proxy disabled by default. Our
> packages should not send telemetry data to Google without explicit opt-in.
What's the reason for treating Go differently than other languages? Fedora does
not patch out calls to sites like npmjs.com, pypi.org, rubygems.org
On Wed Dec 20, 2023 at 07:57 -0800, Brad Smith wrote:
> The go.env file does not, as far as I can tell, contain the original
> values from upstream. Just the modified values. Unless I modified the
> file and cannot recall doing so! My suggestion was to include the
> original upstream settings as co
Greetings -
On Wed, Dec 20, 2023 at 7:35 AM Maxwell G wrote:
>
> Can someone clarify what they mean by this? The patch itself [1] makes
> it pretty clear what the original values are.
When I look at /usr/lib/golang/go.env I see:
[bgsmith@pico newversionprep (main *%)]$ more /usr/lib/golan
On Wed Dec 20, 2023 at 12:14 +0100, Ondrej Pohorelsky wrote:
> On Tue, Dec 19, 2023 at 11:11 PM Neal Gompa wrote:
>
> > On Tue, Dec 19, 2023 at 4:14 PM Brad Smith
> > wrote:
> > >
> > > At a minimum, I recommend that the patch include the original values
> > > for GOPROXY, GOSUMDB, and GOTOOLCHAI
I would personally go with the 2 and get closer to the upstream. I agree
with the npm analogy that was made in the conversation.
Furthermore, I don't think that most users, working on Go projects on
Fedora, would even know that we provide different Go envars
to the upstream ones. IMO, they would ch
On Tue, Dec 19, 2023 at 4:14 PM Brad Smith wrote:
>
> At a minimum, I recommend that the patch include the original values
> for GOPROXY, GOSUMDB, and GOTOOLCHAIN as comments. This makes it
> easier to change back to default values. At the moment, one has to
> visit the relevant web pages.
>
> I l
At a minimum, I recommend that the patch include the original values
for GOPROXY, GOSUMDB, and GOTOOLCHAIN as comments. This makes it
easier to change back to default values. At the moment, one has to
visit the relevant web pages.
I lean towards providing upstream defaults in this case with update
On Tue Dec 19, 2023 at 17:33 +0100, Alejandro Saez Morollon wrote:
> TL;DR: Remove a patch we ship in Go that disables GOPROXY and GOSUMDB and
> follow upstream defaults, or keep it?
I support keeping the Google Go module proxy disabled by default. Our
packages should not send telemetry data to Go
Hi everyone.
TL;DR: Remove a patch we ship in Go that disables GOPROXY and GOSUMDB and
follow upstream defaults, or keep it?
Recently, I had a short conversation in a public forum about two Go
features that we modified in Fedora. GOPROXY and GOSUMDB. As I prepare the
Fedora 40 and Go 1.22 proposa
13 matches
Mail list logo
