Proposal: standardized (subdir) names for 3rdparty/generated code

[Boudewijn Rempt]

Hi,

You've got a good point... I think we need a list to start with. One 
problem I already see is g'mic, which is 3rd party, but not a library and 
so is included directly in the g'mic plugin subtree. But I guess we could 
and should rename the directory it's in to 3rd party.

On Thu, 5 Mar 2015, Friedrich W. H. Kossebau wrote:

> Hi,
>
> when looking through the complete repo for stuff that better is not touched by 
> the planned automated astyle-based reformatting, two kinds of such files were 
> seen:
> * copies of external sources
> * generated files
>
> Could we standardize something about those files, so they can be better 
> handled in anything automated (e.g. scripts, greps) or when trying to get a 
> bigger picture of the code?
>
> What about:
> * putting everything that is basically a copy of code from other projects (and 
> not forked besides minimal patches) in a subdir "3rdparty"
> generated
> * putting everyhing that is committed generated code in a subdir "generated" 
> (and only such code, not the manually written integrating one) 
>
> The subdirs would be either local (makes sense e.g. for most generated stuff, 
> no need to have this somewhere far away from usage) or global (like there is 
> already with "/3rdparty", for stuff that is used by multiple places).
>
> Would anybody think this is a bad idea? Ohter approaches for the problem?
>
> If so, I would work on doing this for master tonight or tomorrow, before the 
> port begins. Or would anybody think that should be done even on 2.9?
>
> Cheers
> Friedrich
> _______________________________________________
> calligra-devel mailing list
> calligra-devel at kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel