[Bug 229476] Review Request: xblast - Lay bombs and Blast the other players of the field (SDL version)

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: xblast - Lay bombs and Blast the other players of the field (SDL version)


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229476





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2007-02-25 09:32 EST -------
Well,

* x11 version problem
----------------------------------------------------------
[tasaka1 at localhost xblast]$ xblast-x11 
could not load font 24
could not load font 18
could not load font 14
-----------------------------------------------------------
  - turns out that this is because x11 version is not compiled
    with "-DMINI_XBLAST" (check x11_config.c). x11 version still
    requests vera font, however vera font is not in the font
    search path.
    BYW according to x11_config.c, x11 version requires some font
    from xorg-x11-fonts-ISO8859???? (note: I think that these
    font packages are not so usual for non-American/European users
    like me).

* gettext translation character corruption
  - well, x11 version does not use gettext, so the sentences
    are always English and have no problem.
  - some character corruption occurs on -sdl version (currently
    I created a link as /usr/share/xblast/locale -> ../locale)
    on both de_DE and fr_FR.

* Directory ownership:
> Actually by doing things that way, combined 
> with the circular deps this has chances are that 
> the directory will not be removed, because xblast-data
> could be removed after xblast-data at which moment it will not be 
> empty.
  - Okay. I catched what you mean. You want to remove
    all packages related to xblast by "yum remove xblast", right?
    Your opinition is reasonable and for this I respect your
    choice.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.