You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update Android RID graph to reflect different posix implementation #43347
Right now Android RID derives directly from linux which is incorrect because in the existing schema linux actually means linux-glibc C standard library.
We have precedent with Alpine which derives from linux-musl and we should do same for Android to derive from linux-bionic instead of linux directly.
Are there other platforms which use bionic? In other words, what sort of reuse will you gain by this indirection vs folks just using android to mean the same thing?
I don’t think will add another RID in between Linux and android if there’s no use case for it. If there’s a specific case for sharing that this would enable then we would consider it. There’s an infinite number of hypothetical characteristics we could model in the RID graph. We only do so when it makes sense to enable sharing. It’s big enough already.
Activity
ericstj commentedon Dec 14, 2020
Are there other platforms which use
bionic? In other words, what sort of reuse will you gain by this indirection vs folks just usingandroidto mean the same thing?marek-safar commentedon Dec 15, 2020
Very minimal right now, this is more a correctness issue than anything else.
ericstj commentedon Dec 15, 2020
I don’t think will add another RID in between Linux and android if there’s no use case for it. If there’s a specific case for sharing that this would enable then we would consider it. There’s an infinite number of hypothetical characteristics we could model in the RID graph. We only do so when it makes sense to enable sharing. It’s big enough already.