Module layout proposal: Split kdegames-data from kdegames

Nicolás Alvarez nicolas.alvarez at
Sat Oct 15 23:58:17 BST 2011

2011/10/14, Parker Coates <parker.coates at>:
> On Fri, Oct 14, 2011 at 14:29, Stefan Majewsky wrote:
>> The added benefit of this solution is that distributions will be
>> encouraged to package data files separately. Because this data (and
>> esp. its format) changes very seldomly only, developers will not need
>> to checkout this giant mass of data from our SCM servers, but can
>> instead use the packages provided by their distribution. The same
>> holds true for drive-by contributors: They only have to clone a tiny
>> repo containing the source code of the game which they want to hack
>> on, without fetching megabytes of data files which they already had
>> installed.
> Personally I don't feel these advantages are significant enough to
> justify doubling the number of packages shipped. Ideally, I would hope
> that distributions will be able to work some magic to merge the
> application and the data files back together again, to create a single
> package per game as they do now. Of course I have no idea if this is
> actually doable.

Many distros already split data and code into two binary packages to
save space, as then they need one code package for every architecture
but only one package for data.

>> 1. Create the new module in SVN, move data files from the current
>> kdegames module. The toplevel directory is still divided by
>> applications, of course.
> Also, will the move preserve history for the data files? While history
> is obviously less essential for data files than it is for source code,
> it'd still be nice to have, especially to guide one to where the data
> used to live.

As long as the move is done with "svn mv" instead of committing all
the files from scratch, history will be preserved.


More information about the kde-core-devel mailing list