rfl...@acsalaska.net rfl...@acsalaska.net wrote:
--=_20120205130645_53400
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi,
I've started working on a port of Zarafa, following
http://wiki.freebsd.org/WantedPorts. I'm not sure if I can finish
On 07.02.2012 02:18, rfl...@acsalaska.net wrote:
Hi,
Thanks for starting to work on it! I've added a link from
WantedPorts
to that
mail.
Currently stuck on the absence of xlocale(3). Is there any chance
these
get MFC'd to RELENG_9 and RELENG_8? Or should I try implementing them
in
On 07.02.2012 02:18, rfl...@acsalaska.net wrote:
Hi,
Thanks for starting to work on it! I've added a link from
WantedPorts
to that
mail.
Currently stuck on the absence of xlocale(3). Is there any chance
these
get MFC'd to RELENG_9 and RELENG_8? Or should I try implementing them
in
in their source
tarball. If that is also the case for zarafa then don't create new
ports for
that but compile the libraries as part of the zarafa port.
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http
then don't create new
ports for
that but compile the libraries as part of the zarafa port.
I decided to go with a slave port for libical as they both use the same
version with unmodified sources. It has the best of both worlds, as I can
decide down the line to make it it's own port if things stray too
Hi,
Thanks for starting to work on it! I've added a link from WantedPorts
to that
mail.
Currently stuck on the absence of xlocale(3). Is there any chance these
get MFC'd to RELENG_9 and RELENG_8? Or should I try implementing them
in platform*.cpp within Zarafa? The latter looks possible, yet
Hi,
I've started working on a port of Zarafa, following
http://wiki.freebsd.org/WantedPorts. I'm not sure if I can finish it,
but I will try my bestest :).
Zarafa has custom patches for libical and libvmime and this is why I have opted
to create 2 supporting ports mail/zarafa-libvmime and
