Open GoogleCodeExporter opened 9 years ago
If this is a packaging issue, then a simple 'rm share/gpick/colors.txt',
executed before building, will get rid of that file. End-users will not have
any problems, apart from reduced number of color names, because Gpick silently
ignores missing color name files.
Scribus is using Resene palettes with the same license for over a year now, so
either nobody noticed, or this is a non-issue.
I am not a lawyer, so I am not qualified to decide if their license complies
with OSD or not.
Original comment by thezbyg
on 18 Jan 2013 at 6:28
I know I can do a simple rm. My worry is more that it probably makes the whole
tarball not totally free.
Would it be possible to make this data downloadable at runtime instead, for
instance?
(For scribus: our maintainers did notice, but in the end, I think they just
dropped the file in the packaging, which is suboptimal)
Original comment by vincent....@gmail.com
on 18 Jan 2013 at 6:39
I could make that file downloadable at runtime, but it would still be optional
(controlled by build-time parameter), because it just doesn't make any sense to
add additional dependencies for a download of a single file.
The tarball would still include that file, but if this somehow infects the
whole tarball, then I could provide a separate tarballs without that
questionable file.
Original comment by thezbyg
on 18 Jan 2013 at 7:09
Download at runtime option added in revision b7dccff730af.
Original comment by thezbyg
on 18 Jan 2013 at 8:04
Original issue reported on code.google.com by
vincent....@gmail.com
on 17 Jan 2013 at 7:03