Summary: Configure option to set version tag to follow
                 Project: Freeciv
            Submitted by: cazfi
            Submitted on: Sun 05 Feb 2012 08:33:16 PM EET
                Category: bootstrap
                Priority: 5 - Normal
                  Status: Ready For Test
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 2.4.0, 2.5.0



Currently there's just one version information sent by metaserver that
client's use to determine if there's newer version of freeciv available.
I find this lacking. Sometimes one may want to follow just bugfix releases
from the same branch, and not incompatible feature releases. Notification
about new stable source code tarball, sometimes weeks before binary is build,
may confuse people who can only use prebuilt windows binaries.
I plan to add metaserver support for several version tags. "Stable" tag would
act just like what we currently have - it would contain latest stable release
from latest branch. Other tags could be created for individual branches, build
types (such as official windows binary using tag "winbuild"), and even things
I have not yet thought of.
While metaserver side has no support for version tags (though the single
version information it has can appear as tag to freeciv side), this patch adds
freeciv side support for building it to use different tags. I'd want this in
before 2.4.0-beta1 since it does change metaserver protocol (
"versions.latest_stable" -> "versions.stable" ) and I rather would not use
earlier version in any release forcing us to maintain it indefinitely to

Once version tags support is added to metaserver, someone wanting to use some
new tag in their freeciv build should contact me for adding tag to
metaserver's list.


File Attachments:

Date: Sun 05 Feb 2012 08:33:16 PM EET  Name: FollowTag.diff  Size: 2kB   By:



Reply to this item at:


  Message sent via/by Gna!

Freeciv-dev mailing list

Reply via email to