Skip to content

native_toolchain_go / go_native_toolchain #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dcharkes opened this issue May 16, 2024 · 5 comments
Closed

native_toolchain_go / go_native_toolchain #2

dcharkes opened this issue May 16, 2024 · 5 comments

Comments

@dcharkes
Copy link

Hi @csnewman!

Cool to see that we have an effort for making Dart and Go work together!

I have preregistered package:native_toolchain_go. If you will actively maintain this package, I'm happy to transfer ownership of that package name to you for consistency between:

It might also be useful for you to chat with @knopp on some best practices and aligning the feature set and APIs. 😃

@csnewman
Copy link
Owner

Hi,

Thanks for reaching out. I had originally hoped to use native_toolchain_go for consistency but couldn't. I'd be happy to switch over to that package name for consistency.

Agreed that the API could do with some cleanup, however I've been deferring this until the Native Assets api becomes more stable.

@dcharkes
Copy link
Author

Thanks for reaching out. I had originally hoped to use native_toolchain_go for consistency but couldn't. I'd be happy to switch over to that package name for consistency.

I can't simply transfer the package immediately to you in the admin page.

You need to be an admin in both publishers to do a transfer.
They can invite you as admin, you do the transfer and then they can remove you from being admin.
Alternatively you may create a third publishers where only you two are admin and it acts only as intermediary.

If you have a publisher, can you invite me as an admin? Then I can transfer the package.

Agreed that the API could do with some cleanup, however I've been deferring this until the Native Assets api becomes more stable.

Probably this one is also relevant for you:

@csnewman
Copy link
Owner

Ah, that's annoying. I've created an intermediary publisher and sent you an invite.

@dcharkes
Copy link
Author

Ah, that's annoying. I've created an intermediary publisher and sent you an invite.

Please invite my google email address: [email protected]

@csnewman
Copy link
Owner

Thanks for transferring the package name. I have now switched over the package to the new name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants