Changes

The components of an installed SME Server are considered to be sorted into the categories below. The categories do not map directly to YUM distribution channels. Each level requires, but does not control, the levels before it.

The components of an installed SME Server are considered to be sorted into the categories below. The categories do not map directly to YUM distribution channels. Each level requires, but does not control, the levels before it.

'''1) The base distribution'''

<ol></li><li>'''The base distribution'''

(the Linux kernel, hardware drivers, network protocols, etc.)This has been, at various times, RedHat, Fedora Legacy, and CentOS.

(the Linux kernel, hardware drivers, network protocols, etc.) This has been, at various times, RedHat, Fedora Legacy, and CentOS.

This category also includes many third-party packages like  Apache, Samba, MySQL, etc. The reason for inclusion here is that these packages are released

This category also includes many third-party packages like  Apache, Samba, MySQL, etc. The reason for inclusion here is that these packages are released and maintained as part of the base distribution. The core developers shall choose the packages in this category.

and maintained as part of the base distribution. The core developers shall choose the packages in this category.

</li><li>'''The core "infrastructure" software'''

'''2) The core "infrastructure" software'''

(e.g. e-smith-lib, firewall base rule set, installer, etc.) The most recent versions of these have been predominately released or repackaged by Mitel, with some community patches. It also includes some third-party packages that are not released as part of the base distribution, and have not been repackaged.

(e.g. e-smith-lib, firewall base rule set, installer, etc.) The most recent versions of these have been predominately

Examples of all the above include djbdns, dovecot, horde, turba, etc. The reason for inclusion here is that these packages are not released as part of the base distribution. The core developers shall choose the packages in this category.

released or repackaged by Mitel,

</li><li>'''Smecore'''

with some community patches. It also includes some third-party packages that are not released as part of the base distribution, and have not been repackaged.

(e.g. i-bays, virtual domains, e-mail) These are custom packages, written specifically for SME Server, sourced from Mitel, e-Smith, and/or the contribs or core developers. These packages are part of the core distribution, and will be supported for any patches or upgrades.

Examples of all the above include djbdns, dovecot, horde, turba, etc. The reason for inclusion here is that these packages are not released as part of the

</li><li>'''Smeaddons'''

base distribution. The core developers shall choose the packages in this category.

These packages have been developed to extend the functionality of SME Server. To the extent possible, given time and resource constraints, an attempt will be made to work with the maintainer to mitigate the affect of any relevant patches or upgrades. These packages are not part of the core distribution.

'''3) Smecore'''

</li><li>'''Smetest packages'''

(e.g. i-bays, virtual domains, e-mail)These are custom packages, written specifically for SME Server, sourced from Mitel, e-Smith, and/or the

These packages have been selected to undergo a testing procedure toward eventual inclusion in the Smeaddons category. They are included here for testing purposes only.

contribs or core developers. These packages are part of the core distribution, and will be supported for any patches or upgrades.

</li><li>'''Smedev packages'''

'''4) Smeaddons'''

These packages have not been tested or examined by the community. These packages might replace software included in the categories below it.

These packages have been developed to extend the functionality of SME Server. To the extent possible, given time and resource constraints, an attempt

The user should understand the implications of using packages in this category, as they may work well, but be incompatible with each other, or cause problems with future system upgrades. No attempt will be made to test the affect of any patches or upgrades on packages in this category.

will be made to work with the maintainer to mitigate the affect of any relevant patches or upgrades. These packages are not part of the core distribution.

'''5) Smetest packages'''

These packages have been selected to undergo a testing procedure toward eventual inclusion in the Smeaddons category. They are included here for testing purposes only.

'''6) Smedev packages'''

These packages have not been tested or examined by the community. These packages might replace software included in the categories below it.

The user should understand the implications of using packages in this category, as they may work well, but be incompatible with each other, or cause

problems with future system upgrades. No attempt will be made to test the affect of any patches or upgrades on packages in this category.

There are some packages that do not fit neatly into these categories. This occurs when one of the base or core packages is modified by anything higher in the list, creating a fork - whether by Smecore, Smeaddon, Smetest, or Smedev category packages. It is the intention of the Contribs community to keep the number of these files as close to zero as possible. In the event that there is seen to be no alternative other than to erase/modify the 'upstream' packages, then the developer will work with the original packager to find an acceptable way to commit the necessary changes to the upstream package or find a solution where the different packages can co-exist. The very last resort would be to create a fork in development. If a package that forks development is created then it should be appropriately labeled as such.

There are some packages that do not fit neatly into these categories. This occurs when one of the base or core packages is modified by anything higher in the list, creating a fork - whether by Smecore, Smeaddon, Smetest, or Smedev category packages. It is the intention of the Contribs community to keep the number of these files as close to zero as possible. In the event that there is seen to be no alternative other than to erase/modify the 'upstream' packages, then the developer will work with the original packager to find an acceptable way to commit the necessary changes to the upstream package or find a solution where the different packages can co-exist. The very last resort would be to create a fork in development. If a package that forks development is created then it should be appropriately labeled as such.

When a particular package is built with the intention of being included in a release, the necessity to fork upstream packages must be agreed upon in advance, by a method to be determined by the core developers and the Development Manager (DM).

When a particular package is built with the intention of being included in a release, the necessity to fork upstream packages must be agreed upon in advance, by a method to be determined by the core developers and the Development Manager (DM).

== Additional Package Details ==

== Additional Package Details ==