No, no android:optional on <uses-permission>. Semantically that is totally different than what am talking about here, which means to still allow being installed even if the device doesn't support the library (or feature since you can do the same <uses-feature>).
On Tue, Jan 19, 2010 at 1:43 AM, Jonas Petersson <[email protected]>wrote: > Hi Dianne, > > > Dianne Hackborn wrote: > >> As of 2.0 I believe there is an additional attribute on uses-library that >> lets you specify that it is optional. >> > > This sounds like a really good step. However, I failed to find it mentioned > in the docs (maybe I'm just looking in the wrong place). > > When this works, could we expect it to also work for uses-permission, as > outlined over a year ago? That would be a really good thing too, IMHO. > > Best / Jonas > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
