On 24.01.2017 09:32, Vincent Cheng wrote: [...] > Strictly speaking, you can accomodate this request by splitting up > src:unknown-horizons into two separate source packages, one which > builds a binary deb that contains the game binary. the other which > builds a binary deb containing all the game data. The only issue with > this approach is that I personally hate mangling upstream source > tarballs, so I only do this if upstream releases separate source > tarballs for the game engine and data (e.g. src:0ad and src:0ad-data). > Punting it over to dpkg's side of the fence is unnecessary IMHO (and I > don't think there's anything reasonable that can be done on the dpkg > side of things that wouldn't be better implemented using the split > source package approach).
This would be another option but due to the reasons you have already mentioned I don't favorite this one. Unknown Horizons is already an arch:all package, so it doesn't waste that much disk space and bandwidth is not really an issue. Upstream releases are not very frequent, the last one was three years ago and splitting the package just because someone has to download 200 MB of data once in a while seems to be overkill. In fact the most precious resources are developer time and human resources in general and the package could benefit from a new human maintainer. Since the bug report raised more general questions it was reasonable to point to dpkg because everything that was mentioned in this bug report is ultimately linked to it. I don't intend to maintain two source packages of Unknown Horizons but everyone else is welcome to do so.
signature.asc
Description: OpenPGP digital signature
