Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread Jeffery Carr
On Friday, December 27, 2024 at 7:17:41 PM UTC-6 Dan Kortschak wrote: On Fri, 2024-12-27 at 17:01 -0800, Jeffery Carr wrote: > I won't go into the nefarious reasons here. Let's just say it's going > to have to be fixed. > > Cryptographically signing this is bad. This kind of argument is unli

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread 'Dan Kortschak' via golang-nuts
On Fri, 2024-12-27 at 17:01 -0800, Jeffery Carr wrote: > I won't go into the nefarious reasons here. Let's just say it's going > to have to be fixed. > > Cryptographically signing this is bad. This kind of argument is unlikely to result in any change. If there is something that you have knowledge

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread Jeffery Carr
On Friday, December 27, 2024 at 6:58:18 PM UTC-6 Sean Liao wrote: It does not exist, and is not possible due to the guarantees the module ecosystem wishes to provide. Any removal request you file only hides the generated documentation. Well, I'm sure it exists. There are a million reasons, all

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread Jeffery Carr
On Friday, December 27, 2024 at 6:56:00 PM UTC-6 Jeffery Carr wrote: On Friday, December 27, 2024 at 6:41:08 PM UTC-6 Sean Liao wrote: The public module ecosystem is backed by a transparency log https://go.dev/ref/mod#checksum-database This doesn't allow you to reuse (change the definition of)

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread 'Sean Liao' via golang-nuts
It does not exist, and is not possible due to the guarantees the module ecosystem wishes to provide. Any removal request you file only hides the generated documentation. - sean On Fri, Dec 27, 2024, 19:46 Jeffery Carr wrote: > On Friday, December 27, 2024 at 6:08:51 PM UTC-6 Dan Kortschak wrote

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread Jeffery Carr
On Friday, December 27, 2024 at 6:41:08 PM UTC-6 Sean Liao wrote: The public module ecosystem is backed by a transparency log https://go.dev/ref/mod#checksum-database This doesn't allow you to reuse (change the definition of) any published module + tag combination observed by the proxy infrast

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread Jeffery Carr
On Friday, December 27, 2024 at 6:08:51 PM UTC-6 Dan Kortschak wrote: On Fri, 2024-12-27 at 15:42 -0800, Jeffery Carr wrote: > The fact of the matter is that sometimes, I make really dumb > mistakes. In the case of versioning things wrong, or making namespace > errors, one needs to redo the nam

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread 'Sean Liao' via golang-nuts
The public module ecosystem is backed by a transparency log https://go.dev/ref/mod#checksum-database This doesn't allow you to reuse (change the definition of) any published module + tag combination observed by the proxy infrastructure. - sean On Fri, Dec 27, 2024 at 6:42 PM Jeffery Carr wrote:

Re: [go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread 'Dan Kortschak' via golang-nuts
On Fri, 2024-12-27 at 15:42 -0800, Jeffery Carr wrote: > The fact of the matter is that sometimes, I make really dumb > mistakes. In the case of versioning things wrong, or making namespace > errors, one needs to redo the namespace from scratch. This means we > need some sort of way of purging name

[go-nuts] "go-import" is great, we need "go-delete"

2024-12-27 Thread Jeffery Carr
The fact of the matter is that sometimes, I make really dumb mistakes. In the case of versioning things wrong, or making namespace errors, one needs to redo the namespace from scratch. This means we need some sort of way of purging namespace paths. As far as I can tell, there is no way to do th