On 12/11/2012 07:35 AM, Joshua Brindle wrote: > I understand that, but it doesn't answer my question :X > > William Roberts wrote: >> Android make files (BoardConfig.mk) follow a hierarchal pattern, I >> follow those makefiles adding in the te files and search paths >> appropriate to that level... So when I build maguro I get Tuna >> (common) and Maguro specific additions because each makefile has their >> additions to the SEPOLICY vars. They are already "included" by their >> subordinates make configs. >> >> >> On Tue, Dec 11, 2012 at 10:47 AM, Joshua >> Brindle<jbrin...@tresys.com> wrote: >>> So, since the device policy variables are BOARD_* how are people >>> here making >>> different policies for different products? It seems very likely that >>> there >>> would be a different policy for carrier1_maguro vs. carrier2_maguro, >>> if only >>> mac_permissions.xml. >>> >>> Any ideas about this? Do I have to make a whole new board for every >>> 'product' now? I don't really like that answer since typically that >>> is a >>> whole new git repo and then keeping X number in sync every time any >>> of them >>> change for a non-product specific reason... >>> >>> -- >>> This message was distributed to subscribers of the seandroid-list >>> mailing >>> list. >>> If you no longer wish to subscribe, send mail to >>> majord...@tycho.nsa.gov >>> with >>> the words "unsubscribe seandroid-list" without quotes as the message. >> >> >> > > -- > This message was distributed to subscribers of the seandroid-list > mailing list. > If you no longer wish to subscribe, send mail to > majord...@tycho.nsa.gov with > the words "unsubscribe seandroid-list" without quotes as the message.
Independent of the SEPOLICY vars issue, how are you maintaining it? -- This message was distributed to subscribers of the seandroid-list mailing list. If you no longer wish to subscribe, send mail to majord...@tycho.nsa.gov with the words "unsubscribe seandroid-list" without quotes as the message.
