On Thu, May 24, 2012 at 5:34 AM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Luiz, > >> > The last profiles addition to BlueZ increased a lot the number of folders we >> > have in the root dir of the project and it looks like more profiles (and more >> > folders) are expected to come. >> > >> > I talked a bit with Johan about changing the hierarchy of the BlueZ tree and >> > the following proposal where 2 new folders are created, 'profiles' and 'libs' >> > and things are moved to them. >> > >> > compat -> /dev/null (will be removed on 5.0) >> > alert -> profiles >> > audio -> profiles >> > cups -> profiles >> > deviceinfo -> profiles >> > health -> profiles >> > input -> profiles >> > lib -> profiles >> > network -> profiles >> > proximity -> profiles >> > sap -> profiles >> > serial -> profiles >> > thermometer -> profiles >> > time -> profiles >> > btio -> libs >> > gdbus -> libs >> > sbc -> libs >> > emulator -> tools >> > mgmt -> tools >> > monitor -> tools >> > attrib >> > doc >> > plugins >> > scripts >> > src >> > test >> > tools >> > unit >> >> Sounds good, the only problem are gdbus and btio, if we merge obexd >> into BlueZ btio will no longer be shared but for gdbus we would have >> to align with other projects as well. > > btio, gdbus, gobex and similar stay top-level. We are not going to > change that. If you are concerned about sharing gdbus patches, git am could do the work for you: "git am --directory=libs/" But I'm not convinced about the "libs" directory... maybe move only profiles? Lucas De Marchi -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
