Restructuring the kdevelop.git folder layout

Kevin Funk kfunk at kde.org
Fri Sep 8 23:16:28 UTC 2017


On Wednesday, 6 September 2017 09:30:37 CEST Kevin Funk wrote:
> On Wednesday, 6 September 2017 01:07:38 CEST Aleix Pol wrote:
> > +1 to the change overall
> > 
> > On Wed, Sep 6, 2017 at 12:33 AM, Sven Brauch <mail at svenbrauch.de> wrote:
> > > On 06/09/17 00:18, Kevin Funk wrote:
> > >> Reasoning:
> > >> - Make it easier to understand the kdevelop.git layout for newcomers.
> > >> - Make the layout more consistent.
> > > 
> > > Looks sensible to me, except one thing maybe: do we really want
> > > languages in plugins/languages/? To me it would also make sense -- and
> > > be shorter and easier to find -- if they were in a dedicated languages/
> > > folder. Sure, they are technically plugins, but ...
> > 
> > I agree that it feels weird, but maybe it's just because 3-level deep
> > is already quite deep?
> 
> True, that's actually a secondary option I had in mind as well, just flatten
> it and put everything into plugins/. To be honest, the categorization
> doesn't buy us much.
> 
> We could even rename a couple of plugins folders to make their intend easier
> to recognize, i.e. 'qmake' -> 'qmakemanager', 'cmake' -> 'cmakemanager'.
> 
> I'm actually unsure what to do, I think I'd even lean towards the "let's
> have them all in one folder" approach. +1.

Other opinions? I'd like to get this into 5.2 branch before the 5.2.0 RC so we 
share the same folder layout on both 5.2 and master branch.

Right now I'm personally leaning towards the layout with no categories at all. 
Makes it even easier to grasp for newcomers IMO.

Just have the plugins in plugins/ as indicated below.

Regards,
Kevin

> FWIW, here's the list of plugins which would end up in plugins/:
> 
> cppcheck
> heaptrack
> common
> gdb
> lldb
> manpage
> qthelp
> astyle
> customscript
> executeplasmoid
> clang
> plugins
> qmljs
> cmakebuilder
> makebuilder
> ninjabuilder
> qmakebuilder
> cmake
> custom-buildsystem
> custommake
> genericprojectmanager
> qmake
> ghprovider
> kdeprovider
> android
> docker
> flatpak
> appwizard
> classbrowser
> codeutils
> contextbrowser
> documentswitcher
> documentview
> execute
> executescript
> externalscript
> filemanager
> filetemplates
> grepview
> konsole
> okteta
> openwith
> outlineview
> patchreview
> problemreporter
> projectfilter
> projectmanagerview
> quickopen
> sourceformatter
> standardoutputview
> switchtobuddy
> testview
> welcomepage
> bazaar
> cvs
> git
> perforce
> subversion
> vcschangesview
> 
> 
> Regards,
> Kevin
> 
> > Maybe it would make sense to have all plugins in plugins
> > (kdevelop/plugns/cmake, kdevelop/plugins/python,
> > kdevelop/plugins/clang).
> > 
> > Aleix


-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170909/081819ea/attachment-0001.sig>


More information about the KDevelop-devel mailing list