Follow-up Comment #17, patch #3719 (project freeciv):
I might also use the same docs and procedure for 2.3.5, when
that happens.
Remembered to do this (just about).
___
Reply to this item at:
http://gna.org/patch/?3719
Update of patch #3719 (project freeciv):
Status:None = In Progress
___
Follow-up Comment #9:
We'll need to modify the docs that go in the regular tarball to
point out the existence of
Update of patch #3719 (project freeciv):
Status: In Progress = Done
Open/Closed:Open = Closed
Planned Release:2.4.0, 2.5.0 = 2.4.0, 2.5.0, 2.6.0
Follow-up Comment #7, patch #3719 (project freeciv):
How hard would it be to drop a suitable tarball out of
make dist?
The short answer is apparently quite hard, so I shouldn't wait for this to
appear to solve this problem.
___
Reply to
Follow-up Comment #8, patch #3719 (project freeciv):
In short, the problem is in how the main tarball then would not depend on gfx
-tarball. Most obviously main tarball's ./configure make dist cannot
build gfx -tarball when gfx is not present.
Follow-up Comment #6, patch #3719 (project freeciv):
I've let this slide for 2.4.0-RC1, but we should do something about it for
2.4.0.
How hard would it be to drop a suitable tarball out of make dist? It's
generally a good idea to avoid manual steps in release processes.
Since downstreams such
Follow-up Comment #5, patch #3719 (project freeciv):
I'm practically following the Debian logic here in that I'm concerned about
preferred form of modification (which is practically the definition of
source code in GPL). Specifically it doesn't matter that we don't have
scripts to automatically
Follow-up Comment #4, patch #3719 (project freeciv):
Something I have seen done for other projects in the past is to distribute a
separate tarball with large assets used to generate graphics, textures,
sounds, etc. in the same distribution locations. This has the advantage of
making it easily
Follow-up Comment #3, patch #3719 (project freeciv):
From our COPYING:
3a) Accompany it with the complete corresponding machine-readable source code,
which must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange; or,
3b) Accompany it
Follow-up Comment #1, patch #3719 (project freeciv):
There is precedent for not distributing components from which distributed
graphics were derived. For instance, data/graphics/ in svn comes to 98Mbyte(!)
and contains huge originals for buildings, wonders etc.
Follow-up Comment #2, patch #3719 (project freeciv):
There is precedent
That doesn't mean it has been handled perfectly, though.
My interpretation is that at least documentation in tarball should tell where
the sources are easily available, and that is entirely sufficient (GPL doesn't
require
URL:
http://gna.org/patch/?3719
Summary: Distributing cimpletoon .blend sources
Project: Freeciv
Submitted by: cazfi
Submitted on: Tue 19 Feb 2013 07:09:07 AM EET
Category: None
Priority: 5 - Normal
12 matches
Mail list logo
