You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

96 lines
3.3 KiB

##
## mailsync.spec -- OpenPKG RPM Package Specification
## Copyright (c) 2000-2022 OpenPKG Project <http://openpkg.org/>
##
## Permission to use, copy, modify, and distribute this software for
## any purpose with or without fee is hereby granted, provided that
## the above copyright notice and this permission notice appear in all
## copies.
##
## THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
## WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
## MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
## IN NO EVENT SHALL THE AUTHORS AND COPYRIGHT HOLDERS AND THEIR
## CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
## SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
## LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
## USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
## ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
## OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
## OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
## SUCH DAMAGE.
##
# package information
Name: mailsync
Summary: Synchronizing Collection of Mailboxes
URL: http://mailsync.sourceforge.net/
Vendor: Tim Culver, Tomas Pospisek
Packager: OpenPKG Project
Distribution: OpenPKG Community
Class: PLUS
Group: Mail
License: GPL
Version: 5.2.1
Release: 20080101
# list of sources
Source0: http://download.sourceforge.net/mailsync/mailsync_%{version}.orig.tar.gz
# build information
BuildPreReq: OpenPKG, openpkg >= 20160101, gcc, bash
BuildPreReq: imap, openssl
PreReq: OpenPKG, openpkg >= 20160101
PreReq: imap, openssl
%description
Mailsync is a way of synchronizing a collection of mailboxes. The
algorithm is a 3-way diff. Two mailboxes are simultaneously compared
to a record of the state of both mailboxes at last sync. New messages
and message deletions are propagated between the two mailboxes. If
you're familiar with CVS, it's the same principle, except there's no
opportunity for conflicts.
%track
prog mailsync = {
version = %{version}
url = http://sourceforge.net/projects/mailsync/files/
regex = mailsync_(__VER__)\.orig\.tar\.gz
}
%prep
%setup -q
%{l_shtool} subst \
-e 's;CCLIENT_LIBS="";CCLIENT_LIBS="%{l_prefix}/lib/libimap.a";' \
-e 's;/include/c-client;/include/imap;' \
configure
%build
libs="-lcrypt"
case "%{l_platform -t}" in
*-sunos* ) libs="$libs -lsocket -lnsl" ;;
esac
CC="%{l_cc}" \
CXX="%{l_cxx}" \
CFLAGS="%{l_cflags -O}" \
CXXFLAGS="%{l_cxxflags -O} -fno-operator-names" \
CPPFLAGS="%{l_cppflags imap openssl}" \
LDFLAGS="%{l_ldflags}" \
LIBS="$libs" \
%{l_bash} ./configure \
--prefix=%{l_prefix} \
--with-openssl=%{l_prefix} \
--with-c-client=%{l_prefix} \
--with-krb5=no \
--with-pam=no
%{l_make} %{l_mflags -O}
%install
%{l_make} %{l_mflags} install AM_MAKEFLAGS="DESTDIR=$RPM_BUILD_ROOT"
strip $RPM_BUILD_ROOT%{l_prefix}/bin/* >/dev/null 2>&1 || true
%{l_rpmtool} files -v -ofiles -r$RPM_BUILD_ROOT %{l_files_std}
%files -f files
%clean