Hi, > > Any hints which groups? I had the impression that Nick was a "Google Android > > engineer"? > > He is, but right now everyone is working on what they consider a top priority > for them and is likely > busy with M related work. Perhaps it would be best to find someone that would > consider this a top > priority in another group. Likely, the NDK google group. > > https://groups.google.com/forum/#!forum/android-ndk
Gee, did they seriously drop the email interface? Or is it just well hidden? I'm not interested in creating some useless google account in order to use a proprietary messaging interface when I have a perfectly fine mail client ... but well, you are not their support contact, I suppose ... ;-) > > Nope. And apart from the fact that it wouldn't work for me, it seems mildly > > crazy > > to me to randomly disable well-established functionality "for security > > reasons" > > and to then expect people to work around the breakage ... > > after all, experience shows that code full of platform-specific workarounds > > tends > > to be so much more reliable and secure than a unified standard-conforming > > portable codebase! /s > > As was said before, Android has never guaranteed a native interface with the > exception > of the (relatively) new NDK. I don't know if hardlinks was ever part of the > Android NDK > stable API. I still don't get that argument ... is the NDK still considered experimental? Just because something is new that doesn't mean it's undefined, does it? This document here specified that the "C library" is part of the "Android API level 3": https://developer.android.com/ndk/guides/stable_apis.html Now, the wording is not particularly specific, they might be referring only to the standard library of the language itself (in which case, it would still be unclear which version of the language ...), while unix-like systems tend to count the POSIX/syscall interface as part of the "C library", but then, they do provide all the headers and stuff that contain all those functions, so that very much suggests that that's part of the "C library", given that nothing to the contrary seems to be documented? > I never really make apps. However, it is defined within the headers > distributed > as part of the NDK (see below). Again, I would hit the NDK group. If they > determine a need, > changes to installd and selinux would likely need to be made. Well, yeah, that's how I managed to get the EACCES ... also, that is code that is running just fine in production on older Android versions. > Also, as an aside, the way you word things might be affecting your level of > support. > Choose your words more carefully. Well, thanks, but I guess I'd rather choose my platform more carefully. I am all for civil and productive discussions, but I am really, really disinterested in being nice to people who think they should interface with people like me tech support style. If someone puts in the effort to create a clear minimal case of something that worked in previous versions but now doesn't work in a new version and there isn't really any obvious reason why it shouldn't, then this is an insult, or at best blatantly incompetent: | Thanks for the suggestion. Our development team has looked into this | defect. This is working as intended. Hard linking files is blocked and an | attempt to call link() on a file will return EACCES. Regards, Florian _______________________________________________ Seandroid-list mailing list Seandroid-list@tycho.nsa.gov To unsubscribe, send email to seandroid-list-le...@tycho.nsa.gov. To get help, send an email containing "help" to seandroid-list-requ...@tycho.nsa.gov.
