[Blends-commit] [SCM] blends-dev branch, master, updated. d2137d6ff69b53705f338d5de7510f0534e4065d

[Andreas Tille]

The following commit has been merged in the master branch:
commit d2137d6ff69b53705f338d5de7510f0534e4065d
Author: Franklin Weng <franklin at ip-server.everfocus.com.tw>
Date:   Tue Apr 1 10:42:04 2014 +0800

    Chapter Chapter 7: add simple description to "adding a new normal package". Appendix A: add some more detail information about how to add new normal packages.

diff --git a/debian/changelog b/debian/changelog
index e1a57c2..41291ed 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,13 @@
 blends (0.6.92) UNRELEASED; urgency=medium
 
+  [ Andreas Tille ]
   * Updated doc
 
- -- Andreas Tille <tille at debian.org>  Fri, 28 Mar 2014 11:14:30 +0100
+  [ Franklin Weng ]
+  * Added EzGo as existing Blend
+  * Better documentation for non-metapackages
+
+ -- Andreas Tille <tille at debian.org>  Fri, 11 Apr 2014 15:56:32 +0200
 
 blends (0.6.91) unstable; urgency=low
 
diff --git a/doc/en/07_starting.xml b/doc/en/07_starting.xml
index 82fb686..584886b 100644
--- a/doc/en/07_starting.xml
+++ b/doc/en/07_starting.xml
@@ -334,6 +334,20 @@ written by Ben Armstrong <email>synrg at debian.org</email>.
 </para>
   </sect2>
 
+<sect2 id="normalpackages">
+ <title>Adding new "normal" packages</title>
+<para>
+  Besides metapackages, you may want to develop some new packages for your blend
+  in order to customize some system behavior, like changing XDG menu style.  Those
+  normal packages are not defined in your tasks, hence we need to define it properly
+  so that blends-dev will know how to package these new, normal packages.  Adding
+  new normal packages is almost identical to debian packaging, just that you need
+  to define your package parameters in debian/control.stub instead of debian/control.
+  Section <xref linkend="developing_normal_packages"/> describes what you need to know for
+  adding new normal packages in Debian Pure Blends in more detail.
+</para>
+</sect2>
+
 </sect1>
 
 <sect1 id="first_release">
diff --git a/doc/en/A_devel.xml b/doc/en/A_devel.xml
index 7e9dbbf..627a81b 100644
--- a/doc/en/A_devel.xml
+++ b/doc/en/A_devel.xml
@@ -652,6 +652,64 @@ behaviour of the tools described below.
 
 </sect1>
 
+<sect1 id="developing_normal_packages">
+  <title>How to develop new normal packages in Pure Blends</title>
+<para>
+  Sometimes you may want to develop new packages for your Pure Blend.  It is almost
+  identical to creating a new debian package.  But in Blends framework you can do it more
+  easily.
+</para>
+<para>
+  Assume that you have already had a well-defined blend.  That is, those necessary files
+  like changelog, compat, copyright and control.stub are in your debian/ folder, maybe
+  with postinst.stub or prerm.stub for task metapackages.  Notice that, all these control
+  and maintainer scripts are just for metapackges defined in your task, not for your new,
+  normal packages since they aren't listed in task.
+</para>
+<para>
+  When you want to develop and add new packages, just like debian packaging, you need to
+  add package informations and parameters in the control file.  However in blends, you should
+  add them in debian/control.stub instead of defining their own control file.  For the
+  maintainer script files, you need to add them in debian/ folder.   However, notice that
+  the maintainer script files should not add ".stub" or blends-dev won't process them.
+</para>
+<para>
+  For example, in blend "foo", we want to add a new normal package "bar".  In debian/control.stub,
+  we may have:
+
+<programlisting>
+Source: foo
+Section: misc
+Priority: extra
+Maintainer: Foo Team <debian-foo at lists.org>
+Uploaders: Foo bar <foo-bar at nowhere.com>
+Build-Depends: debhelper (>= 7), blends-dev (>= 0.6.91)
+Standards-Version: 3.9.3
+Dm-Upload-Allowed: yes
+Homepage: http://foo.bar/
+
+Package: foo-bar
+Architecture: all
+Description: sample blends and packages
+</programlisting>
+</para>
+<para>
+  In the control.stub it defines foo blends, and a new package foo-bar.  Then, in the
+  debian folder, we can add our own preinst, postinst, prerm, and/or postrm maintainer
+  scripts.  However the filename should be foo-bar.preinst, foo-bar.postinst, ... etc.,
+  instead of foo-bar.postinst.stub, since foo-bar doesn't exist in tasks.
+</para>
+
+<para>
+  After those control files are done, you can use
+
+<programlisting>make dist</programlisting>
+
+  to create blends control files, and then use <programlisting>debuild</programlisting>
+  to start packaging.
+</para>
+
+</sect1>
 
 <sect1 id="svn">
   <title>Working with the source repository (<filename>svn</filename> in process of moving to <filename>git</filename>)</title>

-- 
Git repository for blends code