Conventions between tla front-ends

tla itself is not meant to be the canonical, user-friendly interface to arch. It provides low-level and medium-level arch features, but higher level commands can be defined by shell wrappers, GUI interface, ...

While the low-level compatibility is assured by tla, higher-level commands may need a specific configuration file, or any kind of specific interaction with the outside world. It is therefore very important that all front-ends implementing similar features share the same interface to keep a maximal compatibility.

Partner files

implemented by : aba, xtla and Fai.

The directory {arch} may contain a file =partner-versions, which is a newline separated list of fully qualified versions name that are partners of the current version. (This means: Versions from which you often merge)

A file {arch}/+partner-versions may override this file: If it is present, then it will be used instead of =partner-versions

Conventions between front-ends (last edited 2008-07-22 03:00:38 by 64)