mail/installer/removed-files.in
author Geoff Lankow <geoff@darktrojan.net>
Thu, 11 Oct 2018 19:12:45 +1300
changeset 68102 0ada7194b13eac05e0c975aeed32e1effe58a12e
parent 67161 cf4b74f3b01fb3b917e10bc4015771dfc75537d9
child 76460 00750ae0e9d0dd2401f85ec11f67aa08e630a496
child 77267 2f994e763d92961a3400cc78b59a8cd0d45c9cce
permissions -rw-r--r--
Bug 1496632 - Move existing add-on installation UI to notification panels

# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.

# The removed-files.in file specifies files and directories to be removed during
# an application update that are not automatically removed by the application
# update process. The application update process handles the vast majority of
# file and directory removals automatically so this file should not be used in
# the vast majority of cases.

# When to use removed-files.in file to remove files and directories:
# * Files and directories located in the installation's "distribution/" and
#   "extensions/" directories that were added before Thunderbird 27. Files and
#   directories located in these directories were not included in the
#   application update file removals for a complete update prior to Thunderbird 27.
# * Empty directories that were accidentally added to the installation
#   directory.
# * Third party files and directories that were added to the installation
#   directory. Under normal circumstances this should only be done after release
#   drivers have approved the removal of these third party files.

# If you are not sure whether a file or directory should be removed using the
# removed-files.in file please contact one of the developers that work on
# application update.

# Note: the "distribution/" and "browser/extensions/" directories should never
# be removed recursively since these directories are used by Partner builds and
# custom installations.

# To specify a file to be removed add the path to the file.
# * If the file doesn't exist the update will succeed.
# * If the file exists and can't be removed (e.g. the file is locked) the
#   update will fail.
#
# Example: path/to/file

# To specify a directory to be removed only if it is empty add the path to the
# directory with a trailing forward slash.
# * If the directory doesn't exist the update will succeed.
# * If the directory can't be removed (e.g. the directory is locked, contains
#   files, etc.) the update will succeed.
#
# Example: path/to/dir/

# To specify a directory that should be recursively removed add the path to the
# directory with a trailing forward slash and "*".
# * If the directory doesn't exist the update will succeed.
# * If all of the files the directory contains can be removed but the directory
#   or a subdirectory can't be removed (e.g. the directory is locked) the update
#   will succeed.
# * If a file within the directory can't be removed the update will fail.
#
# Example: path/to/dir/*

# Due to Apple Mac OS X packaging requirements files that are in the same
# directory on other platforms must be located in different directories on
# Mac OS X. The following defines allow specifying the Mac OS X bundle
# location which will also work on other platforms.
#
# @DIR_MACOS@
# Equals Contents/MacOS/ on Mac OX X and is an empty string on other platforms.
#
# @DIR_RESOURCES@
# Equals Contents/Resources/ on Mac OX X and is an empty string on other
# platforms.

# An update watershed was required to update to Thunderbird 56 for LZMA and SHA384
# support. This made it possible to delete all of the removal instructions in
# this file.

# Since then, the following were added:

# Remove unpacked lightning extension.
#ifdef NIGHTLY_BUILD
@DIR_RESOURCES@extensions/
@DIR_RESOURCES@extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/*
#else
@DIR_RESOURCES@distribution/
@DIR_RESOURCES@distribution/extensions/
@DIR_RESOURCES@distribution/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/*
#endif