Subversion Repositories prayer

Compare Revisions

Ignore whitespace Rev 104 → Rev 105

/trunk/debian/prayer-templates.install
File deleted
/trunk/debian/prayer-templates-dev.install
0,0 → 1,4
/usr/lib/prayer/template_*
/usr/lib/prayer/*.pl
/usr/include/prayer
/usr/share/prayer/*.make
/trunk/debian/control
14,7 → 14,7
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, adduser, ssl-cert (>= 1.0.11),
logrotate, exim4 | mail-transport-agent
Suggests: prayer-accountd, prayer-templates, imap-server, aspell | ispell
Suggests: prayer-accountd, prayer-templates-src, imap-server, aspell | ispell
Description: standalone IMAP-based webmail server
Prayer is yet another Webmail interface.
.
31,17 → 31,54
 
Package: prayer-templates
Architecture: all
Depends: prayer-templates-src, ${misc:Depends}
Description: dummy package depending on prayer-templates-src
The Prayer template source package is now called prayer-templates-src.
This package can safely be removed after upgrade.
 
Package: prayer-templates-src
Architecture: all
Depends: ${misc:Depends}
Recommends: prayer (>= 1.2.0)
Replaces: prayer (<< 1.2.2.1-6)
Recommends: prayer (>= 1.3.0)
Replaces: prayer-templates (<< 1.3.2-dfsg1-2)
Conflicts: prayer-templates (<< 1.3.2-dfsg1-2)
Suggests: prayer-templates-dev
Description: templates for customizing Prayer Webmail
Prayer is yet another Webmail interface.
.
It is unusual in that it is a complete, standalone, HTTP server and proxy
rather a Apache/mod_php plugin. Prayer maintains persistent connections to
the IMAP server and is written entirely in C. Consequently it is much
faster than most open source Webmail interfaces and puts very little load
on either the machines running the Web server or the backend IMAP servers
(even if traditional Unix format mailfolders are in use).
.
This package contains, in source form, the templates for the HTML
that Prayer outputs.
.
As all the templates are compiled into the session daemon,
prayer-session, you only need to install this package if you need to
As all the templates are included with the main prayer package in
compiled form, you only need to install this package if you need to
customize one or more pages and you want something to start from.
 
Package: prayer-templates-dev
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, make, gcc
Suggests: prayer-templates-src, prayer
Description: tools for compiling Prayer templates
Prayer is yet another Webmail interface.
.
It is unusual in that it is a complete, standalone, HTTP server and proxy
rather a Apache/mod_php plugin. Prayer maintains persistent connections to
the IMAP server and is written entirely in C. Consequently it is much
faster than most open source Webmail interfaces and puts very little load
on either the machines running the Web server or the backend IMAP servers
(even if traditional Unix format mailfolders are in use).
.
Prayer uses its own macro expansion language for the HTML it
outputs. This package contains the programs and scripts needed to
build template libraries, as well as a makefile to facilitate the
process.
 
Package: prayer-accountd
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
/trunk/debian/prayer-templates-dev.README.Debian
0,0 → 1,73
How to build new template packages for Prayer Webmail
=================================================
 
Prayer uses its own macro expansion language, which is documented in
TEMPLATES. The templates (filename extension .t) are first translated
into C code (actually no executable code, merely data structures),
which is then compiled to object form. Originally, the object files
had to be linked with the prayer executables, but as a Debian
extension they can be assembled in shared libraries and loaded
dynamically.
 
This package contains the programs and scripts needed to build
template libraries, as well as a makefile to facilitate the process.
 
 
template-set.make
-----------------
 
/usr/share/prayer/template-set.make can be used directly (via make -f)
or included from an ordinary Makefile.
 
The variable NAME defines the name of the template set. By default
it's set to the name of the current directory. NAME must be set on the
command line or *before* including template-set.make. An alternative
is to follow chapter 3.8 in the GNU Make documentation and _delegate_
certain or all targets to template-set.make:
 
%: force
@$(MAKE) -f /usr/share/prayer/template-set.make NAME=foobar
force: ;
 
The variables TEMPLATES and TEMPLATES_FRONTEND list the top-level
templates that Prayer is known to use, and which should be defined
lest the user be met with a page saying nothing but "Template not
found". Unless all those templates are defined, or you redefine the
variables, the build will fail, but you can set VPATH to a directory
containing an existing template set to take the missing templates from
there. Just be sure that there are no intermediate files lying around!
 
Templates can call other templates by means of the CALL macro. They
are scanned recursively to make sure that all referenced templates are
included in the respective library.
 
A complete template package should consist of two libraries: one for
the session daemon and one for the front-end. The latter contains the
templates for the login screen and certain messages when no session
exists or none can be found, and since the users can't choose the
front-end template set it can be considered pretty much optional. To
skip building the front-end library, set TEMPLATE_LIBS = $(SESSION_LIB)
(also on the command line or before including template-set.make).
 
 
Installing
----------
 
To help build separate architecture-independent and architecture-
specific packages (as well as to avoid conflicts with the "install"
target you may want to use yourself), template-set.make provides two
install targets, "install-sources" and "install-libs", which do the
right thing. The standard DESTDIR variable is supported (instead of
BROOT, which is used in Prayer's own makefiles).
 
 
Images and CSS files
--------------------
 
This package contains no tools to organise static files. Those should
simply be installed in /usr/share/prayer/icons and
/usr/share/prayer/static. Note that Prayer doesn't support sub-
directories, so files should be named in a way that avoids conflicts.
 
 
-- Magnus Holmgren <holmgren@debian.org>, Sun, 25 Oct 2009 18:36:44 +0100
/trunk/debian/changelog
12,8 → 12,12
(under /etc/prayer/templates) to reflect the new template names.
* template_sdk.patch (new): Create makefile for building template set
libraries. Install it together with binaries and scripts needed.
* Rename prayer-templates as prayer-templates-src and add new binary
package prayer-templates-dev containing the aforementioned
template-building tools as well as a README.Debian explaining how to
use it all.
 
-- Magnus Holmgren <holmgren@debian.org> Sun, 25 Oct 2009 19:10:40 +0100
-- Magnus Holmgren <holmgren@debian.org> Sun, 25 Oct 2009 19:11:45 +0100
 
prayer (1.3.2-dfsg1-1) unstable; urgency=low
 
/trunk/debian/prayer-templates-src.install
0,0 → 1,2
usr/share/prayer/templates
usr/include/prayer
/trunk/debian/rules
14,5 → 14,6
DEB_MAKE_INVOKE = $(DEB_MAKE_ENVVARS) $(MAKE)
DEB_MAKE_INSTALL_TARGET = install BROOT=$(CURDIR)/debian/tmp
DEB_INSTALL_CHANGELOGS_ALL = docs/DONE
DEB_INSTALL_DOCS_prayer-templates = --link-doc=prayer-templates-src
DEB_DH_INSTALL_SOURCEDIR = debian/tmp
DEB_INSTALL_MANPAGES_prayer = "--language=C"
/trunk/debian/prayer-templates-dev.docs
0,0 → 1,0
docs/TEMPLATES
/trunk/debian/prayer.install
3,5 → 3,5
usr/sbin/prayer-ssl-prune
usr/share/prayer/icons
usr/share/prayer/static
usr/lib/prayer
usr/lib/prayer/templates/
etc/prayer/prayer.cf