diff options
| author | Daniel Mendler <mail@daniel-mendler.de> | 2023-02-07 18:05:01 +0100 |
|---|---|---|
| committer | Daniel Mendler <mail@daniel-mendler.de> | 2023-02-07 18:07:25 +0100 |
| commit | a9b75e5750dd61adc4cdf00c00f41eb7c9632463 (patch) | |
| tree | 4fe59369a61ab1e33f06f7aa720dce5f170f32fd | |
| parent | ff92d2b5b504db82f61d5d1b7d0fcde41b81ed93 (diff) | |
Manual: Clarify treatment of new libraries
Newly introduced large non-trivial core libraries should either be
published as :core packages or as separately maintained packages on
GNU ELPA. Providing them as part of Compat is infeasible.
| -rw-r--r-- | compat.texi | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/compat.texi b/compat.texi index d15d865..f170a89 100644 --- a/compat.texi +++ b/compat.texi @@ -256,13 +256,15 @@ definitions. The definition belongs to an Emacs core package, which is also distributed via ELPA. Compat does not have to provide backward compatibility for core packages since the updated package can be -installed directly from ELPA. Examples include xref, project, seq, map -and transient. +installed directly from ELPA. Examples include the libraries xref, +project, seq, map and transient. @item New functionality depends on an entire new, non-trivial core library, -which is infeasible to duplicate within Compat while also providing -the necessary backwards compatibility. +which is infeasible to duplicate within Compat. If a backport of such +a library is required, the preferred approach is to either release the +library separately on GNU ELPA as a core package or as a separately +maintained GNU ELPA package. An example is the iso8601 library. @item New functionality was implemented in the C core, or depends on |