martleft.blogg.se

Ufo alien invasion linux
Ufo alien invasion linux









  1. #Ufo alien invasion linux archive#
  2. #Ufo alien invasion linux Patch#
  3. #Ufo alien invasion linux license#

  • Geoscape – the game is about base management and strategy.
  • Two main modes of play: Geoscape mode and Tactical mode.
  • Cooperative team play with multiple players on both sides, up to a maximum of 3 teams for each side, 6 players total.
  • Multiplayer support via LAN or internet.
  • system for player models, powerful artificial intelligence, and many other features.
  • Updated engine has modern OpenGL graphics and special effects, increased texture resolution, hardware-accelerated clipping of map layers for toggling between levels, a new animation.
  • ufo alien invasion linux

    But it’s a stand-alone game and doesn’t require Quake 2 or any other program to run. If I feel sufficiently motivated to double-check all the licensing and look at the bundling over the next few days, I might even submit a new review request.The game engine is based on a heavily modified version of ID’s Quake2 Engine.

    #Ufo alien invasion linux Patch#

    But you can grab my revised spec here:Ī patch from Osipov is mirrored here, along with my configure script patch: And a decision needs to be reached on unbundling. The licensing needs to be checked carefully, and I have not done that (I don't know if the License: tag breakdown that was in the spec is accurate). I'm guessing this separation predated noarch subpackages? This makes the directory ownership logic simpler- if all the packages (data and data-server) included can depend on ufoai-common, ufoai-common can own /usr/share/ufoai and /usr/share/ufoai/base. I don't particularly feel motivated to do it, anyway.īut I will post the updated specs somewhere.Īctually, on further thought, I do not believe it makes sense for ufoai and ufoai-data to be separate source packages. Since we know that horai-ume-fonts has been approved by Fedora Legal, I don't know if there's really a problem with keeping it in this package anymore. I am not sure if this is worth it, honestly, especially given the more lenient bundling guidelines of the present day. pk3 archives, so the pk3s would need to be extracted, content unbundled, and then re-packed. I have yet to take a detailed look at the ufoai-data package, but I am assuming the issue with unbundling things is that all the data files are compressed into. I then had to do some work to get the package to build at all the biggest thing that worries me is that I had to add -Wno-narrowing to CFLAGS to get things to compile, which maybe isn't okay. In particular I patched the configure script so that it does not fail when it receives unrecognized options, meaning that the %configure macro can be used. I have gone through ufoai.spec and cleaned it up, modernizing and fixing some things. Have you received a sufficient answer for packaging it yet? I just saw your email thread in Fedora Legal about the Umefont license. > considered blocker these days if I recall correctly.

    #Ufo alien invasion linux license#

    > would probably apply here too, but not listing any license in the spec is > The page says "You don't have to list this if you don't want to." which > Dmitry suggested that it might be substituted with CopyrightOnly > well, the only problem now is that I cannot find *that much* permissive > does need to be answered, so I'm setting FE-Legal to block it. > don't expect it to be a problem, but that said, this font license question > The Umefont license appears to be an extremely permissive license, so I

    #Ufo alien invasion linux archive#

    > the archive for December suggests that it stopped on Christmas: > note that I also do not see any 2016's messages on e.g. > the list and also an answer from Dmitry Alexandrov > anything for this January while I've already received my e-mail back from > it seems that the archives are broken (or just late?) as I don't see > it seems your email got moderated out of Fedora Legal, as I don't > originally that was done on purpose, not to duplicate the same data in > field (like how the ufoai package spec has it). How about %configure -enable-ufoded -enable-release. ># don't use %%configure, UFOAI doesn't like default configure options I am a newbie maintainer and I would appreciate any help. That's why the package uses prebuilt maps provided by upstream. Note: compiling maps while doable is not recommended by upstream, it is awfully slow and makes checksum issues with multiplayer. Compiling for other architectures should be doable but I'm unable to test it. Upstream - irc:///ufoai best time - evening in Europeīuilding: I built it successfully using mock for i686 and x86_64.

    ufo alien invasion linux

    Licenses: CC-A, CC-A-SA, GPL, GNU FDL, MIT, Public Domain (see ) (made by not me long time ago, denied because of copyright) The long run, you will also have to have a research team study theĪliens and their technologies in order to learn as much as possibleĪbout their technology, their goals and the aliens themselves. Has been founded to face the alien strike force. You are in command of a small special unit which UFO: ALIEN INVASION is a strategy game featuring tactical combatĪgainst hostile alien forces which are about to infiltrate earth at











    Ufo alien invasion linux