On 05.02.2010 22:46, Ulrich Spörlein wrote:
> for the updated port
>
> Update has just been comitted. Simply update your ports tree and update
> it in the usual way.
>
I think mentioning the need to update the configuration file in
pkg-message would still be a good idea, as the syntax for q
On Wed, 03.02.2010 at 22:10:51 +0100, Nicolas Raspail wrote:
> Le 03/02/2010 20:29, Kamigishi Rei a écrit :
>
> Hello
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 03.02.2010 22:12, Nicolas Raspail wrote:
> >
> >> Do you have time to update the port's file to the new 2.1.2
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.02.2010 23:39, Guy Brand wrote:
> Just a note on the installed documentation: # Documentation install
> -d /usr/local/usr/local/share/doc/ejabberd install
> ../doc/guide.html /usr/local/usr/local/share/doc/ejabberd install
> ../doc/*.png /usr/lo
Le 03/02/2010 20:29, Kamigishi Rei a écrit :
Hello
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.02.2010 22:12, Nicolas Raspail wrote:
Do you have time to update the port's file to the new 2.1.2
release of Ejabberd ?
The port was updated on Jan 20th and I have been running it
Kamigishi Rei (spam...@haruhiism.net) on 03/02/2010 at 22:29 wrote:
Hi
> You can fetch the updated port directory at
> http://media.fujibayashi.jp/software/ejabberd.txz (you'll probably
> need archivers/xz to unpack it). Note: it extracts as net-im/ejabberd.
Just a note on the installed document
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.02.2010 22:12, Nicolas Raspail wrote:
> Do you have time to update the port's file to the new 2.1.2
> release of Ejabberd ?
>
The port was updated on Jan 20th and I have been running it ever since:
r...@jail-0-4-2_im ~ # pkg_info|grep ejabberd
Le 24/12/2009 08:36, Kamigishi Rei a écrit :
On 24.12.2009 0:47, Guy Brand wrote:
About absolute pathnames, how should a port refer to /var/spool and
/var/run?
I may be wrong, but the porters handbook doesn't tell a word about
that. So probably your deinstall file is ok.
I thought of using t
On 24.12.2009 0:47, Guy Brand wrote:
About absolute pathnames, how should a port refer to /var/spool and
/var/run?
I may be wrong, but the porters handbook doesn't tell a word about
that. So probably your deinstall file is ok.
I thought of using the localstatedir macro substitution,
Kamigishi Rei (spam...@haruhiism.net) on 17/12/2009 at 04:31 wrote:
Hello
> WARN: /basejail/usr/ports/net-im/ejabberd2/pkg-deinstall: possible use
> of absolute pathname "/var/run/ejabberd".
> WARN: /basejail/usr/ports/net-im/ejabberd2/pkg-deinstall: possible use
> of absolute pathname "/var/s
On 16.12.2009 15:44, Guy Brand wrote:
The port builds and installs properly under 7.1-RELEASE/amd64/R13B02
and 9-CURRENT/amd64/R13B03. pkg_info does not complain at all. That
said portlint shows a few warnings which certainly need to be fixed.
I've corrected some errors it found, however:
Kamigishi Rei (spam...@haruhiism.net) on 15/12/2009 at 22:18 wrote:
Hello,
> http://media.fujibayashi.jp/software/ejabberd2-port.tar.gz (available as
> a hyperlink in that post, too) for the port directory.
> Please also check if you get any warning from pkg_info after the
> installation, too -
On 15.12.2009 22:14, Guy Brand wrote:
I have a question about ejabberd port; the question is related to the
patch that comes with revision 2.0.5_1, patch-919-fileioserver. I'd like
to know if the crash mentioned in the commit message is repeatable, and
what should I do to reproduce it.
I have
On Dec 15, Kamigishi Rei wrote:
Hi
> I have a question about ejabberd port; the question is related to the
> patch that comes with revision 2.0.5_1, patch-919-fileioserver. I'd like
> to know if the crash mentioned in the commit message is repeatable, and
> what should I do to reproduce it.
Hello,
I have a question about ejabberd port; the question is related to the
patch that comes with revision 2.0.5_1, patch-919-fileioserver. I'd like
to know if the crash mentioned in the commit message is repeatable, and
what should I do to reproduce it.
I have updated the port's Makefile, pl
14 matches
Mail list logo
