FS#58923 - [wesnoth] packaging wesnoth-data separately
Attached to Project:
Community Packages
Opened by LightDot (lightdot) - Friday, 08 June 2018, 05:31 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 11 June 2018, 14:59 GMT
Opened by LightDot (lightdot) - Friday, 08 June 2018, 05:31 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 11 June 2018, 14:59 GMT
|
Details
Wesnoth used to be packaged as wesnoth and wesnoth-data.
This greatly reduced the update download size in cases when
just the binaries needed to be updated, which is by far the
most common case.
Recently, wesnoth and wesnoth-data were incorporated into a single wesnoth package. As it is now, every minor update requires a 400 MB download. Please reconsider splitting the package again. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 11 June 2018, 14:59 GMT
Reason for closing: Won't fix
Monday, 11 June 2018, 14:59 GMT
Reason for closing: Won't fix
Comment by
Sven-Hendrik Haase (Svenstaro) -
Monday, 11 June 2018, 14:59 GMT
No, sorry. It's more convenient for me this way and 400 MB is not
a lot of data anymore. Whenever I update wesnoth to a new version
you'll need to get a new data package anyway. The only time this
is convenient is when there is a rebuild and you only get updated
binaries. We originally had a split package because when we had
two architectures we'd otherwise take up twice the space. However,
now that we only have one architecture, there is more benefit to
just having one package (as it saves my time and I don't have to
hunt around when they change their dirs again).