ckage contents (see [[package licensing]]). |
| ''tags''| Keywords/tags that apply to the package, as a white-space separated list of words. This i... tions of packages and for finding packages (see [[packagetags]]). |
**__init__.de script.** Additionally, a p... he title, as that is specified separately.
* **Tags.** It is important that packages are tagged using all the [[package_tags|relevant tags]] since that enables users to locate the package more easily.
* **Zipping.** When distributing a package, the top-level package folder should be
the user interface.
When choosing the title and tags for the package, consider them together: when the user searches f... om adding game names (for example "hexen") in the package title, because Doomsday expects these to be included in the packagetags.
Tags should be used primarily as a tool for allowing the user to find the package. For example, if the user is interested in 3D models for Hexen, they might enter "hexen model" a... that this is separate from and independent of the packagetags. (See the previous example.)
Both the ''recommen
====== Packagetags ======
Packagetags are used for categorizing and flagging packages. It is important to define valid and complete tags for each package because this helps users find the right ones, and... sday will try to automatically guess which game a package is meant to be used for, however you can also manually use these tags in the package metadata. This will override any a
owberry frontend has been responsible for parsing package metadata and deciding which actual files Doomsday... cript]] language. We have put together a new [[fs:package]] format that takes full advantage of FS2 and Doo... er, we will also allow loading old/other resource package formats for backwards compatibility, although the... cular lamp in Doom 2. All assets are described in package metadata using the [[modding:Info]] syntax, and t
* Download a [[http://dengine.net/source|source package]].
* Check out the [[https://github.com/skyjak... hen switch to any release or a specific build via tags. Stable releases are tagged "release-x.y.z".
if the master branch has new commits, and if so, tags and builds a new release. The releases become ava... ts to generate an installable binary distribution package under //distrib/releases//.
The script takes no