Review Request: Storing .kdev4 file in a template subdirectory

Aleix Pol Gonzalez aleixpol at gmail.com
Wed Jul 6 20:39:40 UTC 2011



> On July 6, 2011, 11:41 a.m., Aleix Pol Gonzalez wrote:
> > For starters I think that this should create empty branches and tags directories and just provide source code for trunk, branching should come afterwards. This structure should be provided by the svn support, not for the template. Otherwise you'll end up with at template which it's only purpose is setting up a repository...
> 
> Bastian Schmidt wrote:
>     You mean that the svn support of KDevelop should be able to create this directory structure during the "New Project Wizard" and a project template should only create source code in one of the new directories?
>     
>
> 
> Aleix Pol Gonzalez wrote:
>     Well, we want any template to work on svn, don't we?
> 
> Bastian Schmidt wrote:
>     Yes, you're right. It's better to use any project template with any other vcs.
>     As I know the svn support isn't able to create a directory layout like this
>     
>     - project
>       - branches
>       - trunk
>         - src
>     
>     or any other directory layout. I'm sure this feature will be implemented but in the meantime I 
>     need this feature during the "New Project Wizard". So, the extension of the appwizardplugin
>     could be an intermediate step, until the vcs plugins are able to create a directory layout.
>     
>     Bastian
>     
>     
>     
>     
>

Patches welcome. Currently the svn plugin is not really being developed, you can contribute if you want.

I don't think an SVN template should be provided by KDevelop.


- Aleix


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101853/#review4455
-----------------------------------------------------------


On July 6, 2011, 12:57 p.m., Bastian Schmidt wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/101853/
> -----------------------------------------------------------
> 
> (Updated July 6, 2011, 12:57 p.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Summary
> -------
> 
> Hi,
> we are using project layouts like this:
> 
> project/
>  - branches/
>    - 0.0.1/
>      - bla.kdev4
>      - src/
>      - ...
>  - trunk/         <- development version
>    - bla.kdev4
>    - src/
>    - ...
> 
> As I created an application template for this layout, I recognized that
> kdevelop expect the .kdev4 file in the project root directory. For new
> projects, with this layout, the root directory is project/trunk/. So I need the
> possibility to store the template .kdev4 file in the trunk directory.
> 
> I apply this feature to kdevplatform/plugins/appwizard/appwizardplugin.cpp. The
> attached patch adds 6 lines to appwizardplugin.cpp.
> 
> Patch Description:
> The patch loops through the new project directory and tries to detect the first
> .kdev4 file. If one is found this file will be used. That's all.
> So I can store a template .kdev4 file in any subdirectory.
> 
> Bastian
> 
> 
> This addresses bug 276744.
>     http://bugs.kde.org/show_bug.cgi?id=276744
> 
> 
> Diffs
> -----
> 
>   plugins/appwizard/appwizardplugin.cpp c3ac864 
> 
> Diff: http://git.reviewboard.kde.org/r/101853/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Bastian
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110706/a8c9716d/attachment.html>


More information about the KDevelop-devel mailing list