1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
HOW TO ADD A NEW PLUGIN TO THE PLUGINS BEING BUILT BY THE PACKAGE
-----------------------------------------------------------------
* Add plugin to control
- Add additional Build-Depends:
+ Use a separate line
+ Add them to README.Packaging
- Add Package: entry
+ Depends: claws-mail (>= ${Source-Version}) (allow binNMUs)
- Add package name to claws-mail-extra-plugins Depends:
* Add plugin copyright
- Create package-name.copyright file with the copyright info gathered
* Add plugin documents
- doc files provided to plugin-name.docs.in prefixed by --TOPDIR--/
* Add plugin manpages
- if manpage is Debian provided:
+ copy/create plugin-name.1 manpage to manpages/
+ add manpage to plugin-name.manpages as debian/manpages/plugin-name.1
+ new manpages are preferred in sgml
- else
+ just add it to plugin-name.manpages
+ if you're generating it take care of adjusting the paths
* Add plugin patches
- Give it a unique number and a descriptive name
- use the plugin-name as namespace prefix (plugin-nameXXpatch-name.patch)
* Add plugin to rules
- add patching line to apply-patches: if patches are used
- add build: post $(MAKE) install rules
+ mv original-name-*/* to plugin-name
+ add cleanup rules (if required)
- add docs file generation rule to binary-indep:
- add changelog installation to binary-arch:
* Add plugin to configure
- append '\ name' (without -version) to the TOBEBUILTNAMES var
* Commit and you're almost done
* Check the new plugin is built and packaged ok
--
Ricardo Mones <mones@debian.org>
|
