"kde5" or "kf5" ?

[Sebastian Kügler]

On Saturday, February 16, 2013 10:49:11 Kevin Ottens wrote:
> On Saturday 16 February 2013 10:31:38 Alexander Neundorf wrote:
> > Hi,
> >
> > 
> >
> > AFAIK KDE based on KDE frameworks will not be KDE 5, but still KDE4.
> >
> > 
> >
> > So... I noticed that we install some things to directories containing
> > "kf5", e.g.
> > _set_fancy(PLUGIN_INSTALL_DIR        "${QT_PLUGIN_INSTALL_DIR}/kf5")
> >
> > 
> >
> > but several other things to "kde5":
> > set(BUNDLE_INSTALL_DIR          "/Applications/KDE5")
> > _set_fancy(LIBEXEC_INSTALL_DIR  "${LIB_INSTALL_DIR}/kde5/libexec")
> > _set_fancy(XDG_APPS_INSTALL_DIR
> > "${SHARE_INSTALL_PREFIX}/applications/kde5"
> > )
> >
> > 
> >
> > I think this should be consistent, either "kf5" (which looses the KDE in
> > it) or "kde5".
> 
> I remember having that discussion with David at some point, if I manage to 
> retranscribe the conclusion properly, it was something along the lines of:
>  * If that's where we install parts of the frameworks or runtime
> dependencies  of frameworks it should say kf5;
>  * If that's where we install application parts or metadata it should say 
> kde5.
> 
> So in your example above the use of kf5 vs kde5 doesn't bother me much
> except  for probably libexec which is likely about runtime dependencies of
> frameworks.

There is no kde5.

Everything refering to software, pathes and all that should be kf5. It does 
not make sense for our libs, neither does it make sense for frameworks.

(Branding point of view, ignore at will. :P)
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9