On Sunday 18 September 2011 09:59:57 Sune Vuorela wrote:
> On 2011-09-17, David Faure <[email protected]> wrote:
> >> > Debian and friends uses more or less /usr/lib/NAME/libexec
> >> > where as fedora and friends uses /usr/libexec/NAME/
> > 
> > What's NAME there? The package name, in order to split up the helper
> > binaries from different packages?
> > Do we really need this? After all /usr/bin has no such split.
> 
> NAME there could be package name, but it could also be all sorts of
> other things, like 'kde4'.
> 
> And yes, we need such a split to be sure to avoid clashes. Then several
> libraries can have their own 'domagic' helper executable.
> 
> We have enough issues with avoiding clashes within /usr/bin.

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).

-- 
David Faure, [email protected], http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org).

_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback

Reply via email to