On Sunday, 18 de September de 2011 13:19:53 David Faure wrote: > Right. So would NAME=Qt be enough, or would that still lead to too many > clash risks, between qt apps/frameworks? I guess there could be a > QStringList QStandardPaths::libExecPaths(const QString &packageName = > QString()) > (whose result could be passed as argument to findExecutable), but that seems > slightly overkill to me (compared to simply finding libexec binaries inside > findExecutable, without a specific API for it).
/usr/libexec/OrganisationName/ApplicationName
just like /usr/share/OrganisationName/ApplicationName
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
