[Pkg-pascal-devel] Castle Game Engine 6.0 release in Debian

[Paul Gevers]

Hi Michalis,

On 25-02-17 03:12, Michalis Kamburelis wrote:
> 4. We also released a new version of "view3dscene" 3.16.0 along with
> the new engine ( https://castle-engine.sourceforge.io/view3dscene.php
> ). Due to a lot of engine changes, the latest "view3dscene" source
> code is in practice only compatible with the latest engine version
> (6.0), so you will probably want to update them both
> ("castle-game-engine" and "view3dscene") at once in Debian. Old
> view3dscene will not compile with new CGE -- there were some
> incompatible changes in CGE API (and view3dscene was using some API
> that I treat as "internal"...).

Ok, so here it goes with the first comments ;)

Your generate-code target requires your file-to-pascal-string utility.
Is is worth shipping that with castle-game-engine? Or is it really to
trivial and should I included in view3dscene?

The make target in images depends on image2pascal, while
castle-game-engine now ships image-to-pascal. Trivial patch attached.

Lintian tells me this:
I: view3dscene: desktop-entry-lacks-keywords-entry
usr/share/applications/view3dscene.desktop
N:
N:    This .desktop file does either not contain a "Keywords" entry or
it does
N:    not contain any keywords not already present in the "Name" or
N:    "GenericName" entries.
N:
N:    .desktop files are organized in key/value pairs (similar to .ini
files).
N:    "Keywords" is the name of the entry/key in the .desktop file
containing
N:    keywords relevant for this .desktop file.
N:
N:    The desktop-file-validate tool in the desktop-file-utils package is
N:    useful for checking the syntax of desktop entries.
N:
N:    Refer to
N:
https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s05.html,
N:    https://bugs.debian.org/693918, and
N:    https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords for
N:    details.
N:
N:    Severity: wishlist, Certainty: certain
N:
N:    Check: menu-format, Type: binary

I am able to compile (although I would like to generate all the code
with generate-code target as discussed above). So it should be fine
otherwise.

One last thing. I noticed a file in macosx folder that I don't trust.
Could you please explain the content, license and source of
macosx/template.dmg.bz2?

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-generate-code-target.patch
Type: text/x-diff
Size: 654 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-pascal-devel/attachments/20170327/2f631e77/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-pascal-devel/attachments/20170327/2f631e77/attachment.sig>