Stream: warg

Topic: package transfer and/or reset


view this post on Zulip Robin Brown (Feb 07 2023 at 16:19):

Finally, I'm generally opposed to letting the same package version ever be published twice, but if we do need full deletion that enables re-publishing I think I want this tracked somehow with a "generation" index so that a given combination of (package-name, generation, version) does immutably map to a single piece of content.

view this post on Zulip Lann Martin (Feb 07 2023 at 16:26):

What if the Log ID was derived from name and generation? Then per-package generation monotonicity would be a registry log invariant

view this post on Zulip Robin Brown (Feb 07 2023 at 16:26):

Interesting, you'd have to know the latest generation somehow.

view this post on Zulip Lann Martin (Feb 07 2023 at 16:27):

Actually, what if generation went in the package init message?

view this post on Zulip Lann Martin (Feb 07 2023 at 16:28):

I guess that sort of breaks decoupling from the package name

view this post on Zulip Robin Brown (Feb 07 2023 at 16:29):

More broadly, it makes the package internally the authority about things we haven't previously let it

view this post on Zulip Robin Brown (Feb 07 2023 at 16:35):

There's a lot of ways of incorporating generation numbers into the system and it's a big design question I want us to think carefully about.

view this post on Zulip Robin Brown (Feb 07 2023 at 16:36):

I think there's also some overlap here between generations, package transfer, and rolling up state that we should think about.

view this post on Zulip Notification Bot (Feb 07 2023 at 16:37):

8 messages were moved here from #warg > package namespacing by Kyle Brown.


Last updated: Dec 23 2024 at 12:05 UTC