Get project updates, sponsored content from our select partners, and more. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.īzflag-admin-2.4.25-alt0.git_1_a24915.x86_64īzflag-admin-debuginfo-2.4.25-alt0.git_1_a24915.x86_64īzflag-debuginfo-2.4.25-alt0.git_1_a24915.x86_64īzflag-server-debuginfo-2.4.25-alt0.git_1_a24915.x86_64īzflag-server-2.4.25-alt0.git_1_a24915. BZFlag has undergone several different numbering schemes over the years (decades) that can be roughly categorized as follows: the 1.7 alphabet soup series, the 1.10 through 2. Download Latest Version bzflag-2.4.22.zip (15.8 MB) Get Updates.
#BZFLAG 2.4 LICENSE#
This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. BZFlag is licensed under the LGPL 2.1 and MPL 2.0 and is free to use/distribute/modify as long as the terms of the license are followed. The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them. var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. The package have SysV init script(s) but no native systemd files.įound a subdir in /var/run or /var/lock. etc/rc.d/init.d/bzfs: not systemd compatible: lsb init header missing and rvice is not present.
#BZFLAG 2.4 UPDATE#
With all that said, people seem to like this game, I may check it out later!Įdit: Looks like they added a tagline to the page. Log message: Update bzflag to 2.4.14 From Charlene Wendling While here, update license marker and COMPILER comment. You don't necessarily need to have a tagline like that on every release page or documentation page, but if I end up on your site and delete everything from the URL except "", I should be 2 seconds away from a simple description of what your project is.
This could've been fixed by just having an h2 and a paragraph at the top saying "BZFlag" and "An open source tank-based warfare game with online multiplayer, going strong since 2008!" (or whenever the project started) I guess this is a game where you drive tanks? I'll take a look at the comments. "A Flying tank", "Tanks with Superpowers". > Hmm, the project news doesn't tell me much. Is this a game engine? A physics simulator? Maybe if I scroll down I'll find out > A picture of some 3D rendered stuff, and download links for a bunch of platforms. > BZFlag? Does this have something to do with zipping files? Meh, I'll click and see what it is. Here's what I thought when I clicked this link: This page documents user visible changes to the BZFlag server for the 2.4 release of BZFlag.
#BZFLAG 2.4 SOFTWARE#
I've made a couple of comments like this on HN before, but whenever you make a homepage for a project, whether it's a game, game engine, software library, command line tool or anything-please start by describing what the thing is in one or two sentences. For version 2.4 there are new requirements for your server to be listed on the BZFlag hosted server list.
0 kommentar(er)
