Project

General

Profile

Feature #1761

Feature #1601: Package management

FS2 resource packages

Added by skyjake about 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Redesign
Target version:
Start date:
2014-04-18
% Done:

100%


Description

There are already conventions in place for resource packaging in FS2:
  • zipped folders with .pack, .save, etc. extension
  • Info (ScriptedInfo) metadata

However, the Snowberry resource package formats also need to be understood by the file system.

For full fledged package management, though, the file system needs to know which packages are in use and which ones are not.

Also see the Resource package proposal.


Related issues

Related to Feature #1766: Server-supplied (i.e., remote) resource filesClosed2014-04-18

Precedes Feature #1834: Import Snowberry addon formats as Doomsday 2 packagesClosed2014-04-19

History

#1 Updated by skyjake about 8 years ago

  • Description updated (diff)

#2 Updated by skyjake about 8 years ago

  • Description updated (diff)

#3 Updated by skyjake almost 8 years ago

  • Assignee set to skyjake
  • Target version set to 1.15
  • % Done changed from 0 to 80

#4 Updated by skyjake almost 8 years ago

  • Precedes Feature #1834: Import Snowberry addon formats as Doomsday 2 packages added

#5 Updated by skyjake almost 8 years ago

  • Status changed from New to Closed
  • % Done changed from 80 to 100

#6 Updated by skyjake almost 8 years ago

The basic operating principles of FS2 packages are now in place:
  • package metadata stored in container file's metadata
  • symlinks to loaded packages under /packs
  • package assets and asset symlinks
  • observing availability of packages and assets
  • DS hooks for load/unload
  • file indexing that takes packages into account

Also available in: Atom PDF