Open-Xchange Customer Repository Structure

From Open-Xchange
Revision as of 07:59, 26 August 2011 by Choeger (talk | contribs)

Organization of the Open-Xchange private repository

As a customer with a special support contract you will receive patches for critical problems in a special directory which can only accessed by you, personally.

This repository has a consistent layout:

6.18.2
    \ 
      - custom
      - ptf
6.20
    \ 
      - custom
      - ptf

[...]

You will find your patches organized within top-level folders matching the version of the release you are currently using. Within these folders, you will always find

  1. a folder custom which contains individual customizing or manually uploaded stuff which does not fit into our automated processes.
  2. a folder ptf which contains individual bugfix patches as you requested them. These are automatically maintained by our internal workflow- and buildsystem.

Within the folder ptf, you will find repositories containing packages for all linux platforms you are maintaining:

ptf_yyyy-mm-dd_yyyymmddnnnnnnnn_ldbaccount
ptf_yyyy-mm-dd_yyyymmddnnnnnnnn_ldbaccount

[...]

Each of them contain

DebianLenny
DebianLenny_all
Release_Notes_PTF_for_Ticket_yyyymmddnnnnnnnn_ldbaccount_yyyy-mm-dd.pdf
RHEL6
RHEL6_all

[...]

As we only build the packages containing the bugfixes for your problem, we also provide "consolidated" repositories containing all our packages. These have the suffix _all. These directories contain symlinks to the matching version of this build within http://software.open-xchange.com/X.YY/updates. However, with the next public patch release, these symlinks will become stale which means they will be removed then and instead you will find this:

DebianLenny
DebianLenny_all.readme
RHEL6
RHEL6_all.readme

[...]