Re: new net/tkabber
On 2014/03/22 03:07, Dmitrij D. Czarkoff wrote: Hello! Tkabber is a fully-featured client for a Jabber instant messaging system. It is written in Tcl/Tk and has many features like support of unicode, ssl support, http proxy, file transfers and support of multi-user conference protocol. -- Dmitrij D. Czarkoff base/pkg/README: - should recommend packages (which anyone can install with pkg_add) rather than port names (which need an unpacked ports tree), i.e. - tclgpg isn't in ports, should be removed from the list until it's added. let's get this in first though before we add that...you've been waiting long enough :-( plugins/pkg/README - same, please recommend packages rather than ports Apart from this, it's OK with me, so if someone would like to either import it or give me an OK ...
Re: new net/tkabber
Stuart Henderson said: base/pkg/README: - should recommend packages (which anyone can install with pkg_add) rather than port names (which need an unpacked ports tree), i.e. [...] plugins/pkg/README - same, please recommend packages rather than ports Thanks! Port with packages instead of ports in README attached. - tclgpg isn't in ports, should be removed from the list until it's added. I'm preparing a port, but: 1. I didn't get it to build yet and 2. It was not released yet - main developer (as listed on Google Code project page) says it isn't ready for stable release. So I removed tclgpg from README for now. -- Dmitrij D. Czarkoff tkabber.tgz Description: application/tar-gz
new net/tkabber
Hello! Tkabber is a fully-featured client for a Jabber instant messaging system. It is written in Tcl/Tk and has many features like support of unicode, ssl support, http proxy, file transfers and support of multi-user conference protocol. -- Dmitrij D. Czarkoff tkabber.tgz Description: application/tar-gz
Re: NEW net/tkabber
On Tue, Mar 05, 2013 at 01:24:07PM +0100, Sebastian Reitenbach wrote: speaking of coccinella, there its done, because the jabber xml stream is contigous, from login to logout, and the xml parser doesn't like it if some tags are not closed before then end of the stream, so, before logout. The coccinella tclxml is patched to work with that constraint. Tkabber does it for the same reason (from README): Support for _TclXML_ as an external XML parser has been removed (since _TclXML_ has anyway been unable to support partial XML processing) along with the global variable use_external_tclxml which controlled the loading of _TclXML_. They support unmodified tDOM as external parser though. -- Dmitrij D. Czarkoff
Re: NEW net/tkabber
On 03/05/13 12:16, Dmitrij D. Czarkoff wrote: On Tue, Mar 05, 2013 at 01:24:07PM +0100, Sebastian Reitenbach wrote: speaking of coccinella, there its done, because the jabber xml stream is contigous, from login to logout, and the xml parser doesn't like it if some tags are not closed before then end of the stream, so, before logout. The coccinella tclxml is patched to work with that constraint. Tkabber does it for the same reason (from README): Support for _TclXML_ as an external XML parser has been removed (since _TclXML_ has anyway been unable to support partial XML processing) along with the global variable use_external_tclxml which controlled the loading of _TclXML_. They support unmodified tDOM as external parser though. Thanks! Stu
Re: NEW net/tkabber
On 03/04/13 13:25, Dmitrij D. Czarkoff wrote: On Wed, Jan 30, 2013 at 04:05:28PM +0300, Kirill Bychkov wrote: Hi. This is a port of tkabber-0.11.1, Tk Jabber client. It was sent to ports by Anton Yabchinskiy in Nov 200 and by Dmitrij Czarkoff four years later in Nov 2012. I'm using it on i386 and amd64 since it was first submitted to ports@ by Anton. This is reworked port, partly based on a work of previous submitters. Comments? OKs? The port builds and runs fine. Still I would suggest the following changes: As I mentioned in my last message, I get crashes when trying to login to a server. Mind you, I don't know jabber well, so any tips are welcome. == --- a/net/tkabber/base/pkg/README Mon Mar 04 18:24:27 2013 +0100 +++ b/net/tkabber/base/pkg/README Mon Mar 04 19:24:50 2013 +0100 @@ -11,4 +11,3 @@ * textproc/ispell (spell checking) * x11/tkcon (Tk console) * x11/tktray (iconify Tkabber) -* x11/xosd (OSD support) Why not just have these as RUN_DEPENDS? Give the user the maximum experience. About PLIST change: tkabber-khim plugin uses bundled KHIM package, which requires Tk 8.4. As I get it, KHIM is now a part of tklib, so I think it would be better to comment the bundled KHIM out and suggest devel/tklib dependency in README then to tie the package to Tk 8.4. Thanks for spotting this. It would be greatly appreciated if existing packages (like KHIM, part of tklib) could be used instead of the bundled ones. I also notice a TclXML in there, maybe that can be excised as well? KHIM doesn't need 8.4. Nothing needs 8.4. [package require Tcl 8.4] tends to mean *minumum* 8.4. Tkabber seems fine in 8.6. Tcl script-only packages should run fine under 8.[56]. Tcl extensions compiled against 8.5 should be [load]able into 8.6. 8.4 is the past. 8.5 is the present. 8.6 is the future. Let's look to the future. Stu
Re: NEW net/tkabber
On Mon, Mar 04, 2013 at 01:18:56PM -0500, Stuart Cassoff wrote: The port builds and runs fine. Still I would suggest the following changes: As I mentioned in my last message, I get crashes when trying to login to a server. Mind you, I don't know jabber well, so any tips are welcome. Could you please describe the problem in more details? Any error messages? Any output to terminal? == --- a/net/tkabber/base/pkg/README Mon Mar 04 18:24:27 2013 +0100 +++ b/net/tkabber/base/pkg/README Mon Mar 04 19:24:50 2013 +0100 @@ -11,4 +11,3 @@ * textproc/ispell (spell checking) * x11/tkcon (Tk console) * x11/tktray (iconify Tkabber) -* x11/xosd (OSD support) Why not just have these as RUN_DEPENDS? Give the user the maximum experience. I'm not sure whether forcing optional dependencies is a good idea: any of these may happen to be an optional dependency elsewhere, so it may break things. I believe I had some problems of the kind with xosd before, and ISpell may also get caught up somewhere. IMO it's generally wise to keep optional things up to users. Thanks for spotting this. It would be greatly appreciated if existing packages (like KHIM, part of tklib) could be used instead of the bundled ones. I also notice a TclXML in there, maybe that can be excised as well? I'll look into it later. KHIM doesn't need 8.4. Nothing needs 8.4. [package require Tcl 8.4] tends to mean *minumum* 8.4. I'm not particularly sure why I thought KHIM needed 8.4. Probably I had a reason to think so. -- Dmitrij D. Czarkoff
Re: NEW net/tkabber
On 03/04/13 16:39, Dmitrij D. Czarkoff wrote:
On Mon, Mar 04, 2013 at 01:18:56PM -0500, Stuart Cassoff wrote:
The port builds and runs fine. Still I would suggest the following changes:
As I mentioned in my last message, I get crashes when trying to login to a
server.
Mind you, I don't know jabber well, so any tips are welcome.
Could you please describe the problem in more details? Any error messages? Any
output to terminal?
can't set lib(1,sessionid): can't read lib(1,sasltoken): no such element in
array
can't read lib(1,sasltoken): no such element in array
while executing
$lib($connid,sasltoken) auth -command [list [namespace current]::login_aux5
$connid $cmd]
(procedure login_aux3 line 7)
invoked from within
...
Full err log attached.
Why not just have these as RUN_DEPENDS?
Give the user the maximum experience.
I'm not sure whether forcing optional dependencies is a good idea: any of
these may happen to be an optional dependency elsewhere, so it may break
things. I believe I had some problems of the kind with xosd before, and ISpell
may also get caught up somewhere.
IMO it's generally wise to keep optional things up to users.
*shrug*
Personally, as a dummy who's not entirely familiar with tkabber I may
possibly install tkabber and never read the README and thus think
that obsd's tkabber lacks features.
But that's just me. Most users are probably smarter.
I'm not particularly sure why I thought KHIM needed 8.4. Probably I had a
reason to think so.
Maybe because khim.tcl contains:
package require Tcl 8.4
package require Tk 8.4
Stu
can't set lib(1,sessionid): can't read lib(1,sasltoken): no such element in
array
can't read lib(1,sasltoken): no such element in array
while executing
$lib($connid,sasltoken) auth -command [list [namespace current]::login_aux5
$connid $cmd]
(procedure login_aux3 line 7)
invoked from within
login_aux3 $connid $cmd
(procedure login_aux1 line 9)
invoked from within
login_aux1 $connid $cmd
(procedure ::jlib::login_aux line 9)
invoked from within
::jlib::login_aux 1 {recv_auth_result 1 {proxyuseragent {Mozilla/4.0
(compatible; MSIE 6.0; OpenBSD 5.3)} resource t...@tach.tclers.tk sslcertfile
{} p...
(uplevel body line 1)
invoked from within
uplevel #0 $cmd
(procedure ::jlib::wait_for_stream_aux line 6)
invoked from within
::jlib::wait_for_stream_aux 1 {::jlib::login_aux 1 {recv_auth_result 1
{proxyuseragent {Mozilla/4.0 (compatible; MSIE 6.0; OpenBSD 5.3)} resource
tcl@...
(write trace on lib(1,sessionid))
invoked from within
set lib($connid,sessionid) $sessionid
(procedure ::jlib::got_stream line 16)
invoked from within
::jlib::got_stream 1 {xmlns http://etherx.jabber.org/streams from
all.tclers.tk id fgmeodime8hbwg6rbydxi3uqpq7s5ieky1zneiat version 1.0}
(uplevel body line 1)
invoked from within
uplevel #0 $wrapper($id,streamstartcmd) [list $newvarlist]
(procedure ::jlib::wrapper:elementstart line 44)
invoked from within
::jlib::wrapper:elementstart wrap#8 stream {from all.tclers.tk id
fgmeodime8hbwg6rbydxi3uqpq7s5ieky1zneiat version 1.0} -namespace
http://etherx.jabbe...;
(uplevel body line 1)
invoked from within
uplevel #0 $options(-elementstartcommand) [list $tag $attr1] $empty $ns
$nsdecls
invoked from within
ParseEvent:ElementOpen $tag $param [array get options]
invoked from within
::sgml::parseEvent {{} {} {} {} ?xml {} { version='1.0'?} {} stream:stream {}
{ xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' ...
(eval body line 1)
invoked from within
eval ::sgml::parseEvent [list $tokenised] $parseOptions
(procedure parse line 62)
invoked from within
parse _parser_wrap#8 {?xml version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='all.tclers.tk' v...
(in namespace inscope ::xml::tclparser script line 1)
invoked from within
::namespace inscope ::xml::tclparser parse _parser_wrap#8 {?xml
version='1.0'?stream:stream xmlns:stream='http://etherx.jabber.org/streams'
xmlns='...
(eval body line 1)
invoked from within
eval $classinfo(-parsecommand) [list $name] $args
(procedure ::xml::ParserCmd line 48)
invoked from within
::xml::ParserCmd _parser_wrap#8 parse {?xml version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from=...
(eval body line 1)
invoked from within
eval ::xml::ParserCmd _parser_wrap#8 [list $method] $args
(procedure ::jlib::_parser_wrap#8 line 1)
invoked from within
::jlib::_parser_wrap#8 parse {?xml version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='all.tcle...
(uplevel body line 1)
invoked from within
uplevel 1 [list $wrapper($id,parser)] $args
(procedure wrapper:parser line 7)
invoked from within
wrapper:parser $lib($connid,wrap) parse $msg
(procedure jlib::inmsg
Re: NEW net/tkabber
On Tue, March 5, 2013 00:39, Dmitrij D. Czarkoff wrote: On Mon, Mar 04, 2013 at 01:18:56PM -0500, Stuart Cassoff wrote: The port builds and runs fine. Still I would suggest the following changes: As I mentioned in my last message, I get crashes when trying to login to a server. Mind you, I don't know jabber well, so any tips are welcome. Could you please describe the problem in more details? Any error messages? Any output to terminal? == --- a/net/tkabber/base/pkg/README Mon Mar 04 18:24:27 2013 +0100 +++ b/net/tkabber/base/pkg/README Mon Mar 04 19:24:50 2013 +0100 @@ -11,4 +11,3 @@ * textproc/ispell (spell checking) * x11/tkcon (Tk console) * x11/tktray (iconify Tkabber) -* x11/xosd (OSD support) Why not just have these as RUN_DEPENDS? Give the user the maximum experience. I'm not sure whether forcing optional dependencies is a good idea: any of these may happen to be an optional dependency elsewhere, so it may break things. I believe I had some problems of the kind with xosd before, and ISpell may also get caught up somewhere. IMO it's generally wise to keep optional things up to users. I totally agree. Thanks for spotting this. It would be greatly appreciated if existing packages (like KHIM, part of tklib) could be used instead of the bundled ones. I also notice a TclXML in there, maybe that can be excised as well? I'll look into it later. KHIM doesn't need 8.4. Nothing needs 8.4. [package require Tcl 8.4] tends to mean *minumum* 8.4. I'm not particularly sure why I thought KHIM needed 8.4. Probably I had a reason to think so. -- Dmitrij D. Czarkoff Dmitrij, I thought you've lost interest in tkabber, but now it seems you're not. I have no time atm to polish it before submission. Feel free to take maintainership. Latest version could be found in openbsd-wip on github.
NEW net/tkabber
Hi. This is a port of tkabber-0.11.1, Tk Jabber client. It was sent to ports by Anton Yabchinskiy in Nov 200 and by Dmitrij Czarkoff four years later in Nov 2012. I'm using it on i386 and amd64 since it was first submitted to ports@ by Anton. This is reworked port, partly based on a work of previous submitters. Comments? OKs? From base/DESCR: Tkabber is a fully-featured client for a Jabber instant messaging system. It is written in Tcl/Tk and has many features like support of unicode, ssl support, http proxy, file transfers and support of multi-user conference protocol. tkabber.tar.gz Description: GNU Zip compressed data
Re: NEW net/tkabber
On 2008-07-13 22:03:37+0200, viq wrote:
I played a bit with it on i386, and it basically works. Though I would
make it depend on security/tcltls, or at least mention it, I don't like
connecting to servers over plaintext. It also made me patch a small
buglet in tcltls and make tcltls and bwidgets depend on tcl 8.5 - I
don't see a good reason for a port depending on tcl 8.5 depend on ports
depending on tcl 8.4 ;)
I didn't get around trying to make it work with gnupg, that would be
nice too.
Patches for security/tcltls and x11/bwidget below.
--
viq
Thanks for your feedback. Somehow I have missed that security/tcltls
port, of course tkabber should depend on it. Also I have renamed
USE_TK_VERSION to TK_VERSION in Makefile.
As I know tclgpgme is very outdated binding and requires version 0.3.x
of gpgpme to build. So it looks like a problem: tclgpgme binding should
be updated (or reimplemented from scratch) to comply with current gpgme
version or outdated 0.3.x version of gpgme should be included in the ports
tree.
What about tkabber-plugins distributed from ${HOMEPAGE}? Some of them are
useful and it will not be too hard to port them too. Should they be
packaged with main tkabber package or should I use multi-packages? Or
maybe create separate net/tkabber-plugins port?
Updated port attached. Please test/use.
tkabber-0.11.0.tar.gz
Description: application/tar-gz
Re: NEW net/tkabber
On Mon, Jul 14, 2008 at 01:04:15PM +0400, Anton V. Yabchinskiy wrote:
On 2008-07-13 22:03:37+0200, viq wrote:
I played a bit with it on i386, and it basically works. Though I would
make it depend on security/tcltls, or at least mention it, I don't like
connecting to servers over plaintext. It also made me patch a small
buglet in tcltls and make tcltls and bwidgets depend on tcl 8.5 - I
don't see a good reason for a port depending on tcl 8.5 depend on ports
depending on tcl 8.4 ;)
I didn't get around trying to make it work with gnupg, that would be
nice too.
Patches for security/tcltls and x11/bwidget below.
--
viq
Thanks for your feedback. Somehow I have missed that security/tcltls
port, of course tkabber should depend on it. Also I have renamed
USE_TK_VERSION to TK_VERSION in Makefile.
I will look at that. Also there is newer version of tcltls available, it
could probably use an update, and modification to use the tcl module.
As I know tclgpgme is very outdated binding and requires version 0.3.x
of gpgpme to build. So it looks like a problem: tclgpgme binding should
be updated (or reimplemented from scratch) to comply with current gpgme
version or outdated 0.3.x version of gpgme should be included in the ports
tree.
Yeah, I noticed that, and that should be fixed somehow, but I didn't
research the subject yet.
What about tkabber-plugins distributed from ${HOMEPAGE}? Some of them are
useful and it will not be too hard to port them too. Should they be
packaged with main tkabber package or should I use multi-packages? Or
maybe create separate net/tkabber-plugins port?
They have additional dependencies (latex, ImageMagic, osd, to start) so
I am against putting them in same port, either multi-packages, or
separate port (maybe with sub-packages?). Also we'd need to check whether
there is an option to selectively enable/disable them, from a quick look
at README they suggest installation consisting of copying appropriate
plugin dirs to ~/.tkabber/plugins/
Updated port attached. Please test/use.
I'll have a look at it, thank you.
--
viq
Re: NEW net/tkabber
On Wed, Jun 11, 2008 at 02:19:23PM +0400, Anton V. Yabchinskiy wrote:
Hello, [EMAIL PROTECTED] Here is a nice jabber client. From pkg/DESCR:
Tkabber is a free and Open Source client for the Jabber instant
messaging system. It's written in Tcl/Tk, and works on many platforms.
Tkabber is fully-featured Jabber client. For the full list of
features see http://tkabber.jabber.ru/files/doc/tkabber.html#s.features
Works on i386 (and on any other arch I think because of Tcl/Tk).
No build required.
I played a bit with it on i386, and it basically works. Though I would
make it depend on security/tcltls, or at least mention it, I don't like
connecting to servers over plaintext. It also made me patch a small
buglet in tcltls and make tcltls and bwidgets depend on tcl 8.5 - I
don't see a good reason for a port depending on tcl 8.5 depend on ports
depending on tcl 8.4 ;)
I didn't get around trying to make it work with gnupg, that would be
nice too.
Patches for security/tcltls and x11/bwidget below.
--
viq
Index: Makefile
===
RCS file: /cvs/ports/security/tcltls/Makefile,v
retrieving revision 1.3
diff -u -d -r1.3 Makefile
--- Makefile7 Jul 2008 17:31:20 - 1.3
+++ Makefile13 Jul 2008 19:58:58 -
@@ -4,7 +4,7 @@
VERSION= 1.5.0
DISTNAME= tls${VERSION}-src
-PKGNAME= tcltls-${VERSION}p0
+PKGNAME= tcltls-${VERSION}p1
SHARED_LIBS= tls150 0.0
CATEGORIES=security lang/tcl
@@ -27,7 +27,7 @@
BUILD_DEPENDS= ${RUN_DEPENDS}
TCLTLS=tls1.5
-TCL_VERSION= 8.4
+TCL_VERSION= 8.5
SUBST_VARS+= TCLTLS
CONFIGURE_STYLE=gnu
Index: patches/patch-pkgIndex_tcl_in
===
RCS file: patches/patch-pkgIndex_tcl_in
diff -N patches/patch-pkgIndex_tcl_in
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-pkgIndex_tcl_in 13 Jul 2008 19:58:58 -
@@ -0,0 +1,10 @@
+$OpenBSD$
+--- pkgIndex.tcl.in.orig Fri Jul 11 19:56:13 2008
pkgIndex.tcl.inFri Jul 11 19:56:32 2008
+@@ -5,5 +5,5 @@
+ #replace the original which didn't include the commands from tls.tcl.
+ #
+
+-package ifneeded tls 1.5 [list load [file join $dir @RELPATH@ @[EMAIL
PROTECTED] ] ; [list source [file join $dir tls.tcl] ]
++package ifneeded tls 1.50 [list load [file join $dir @RELPATH@ @[EMAIL
PROTECTED] ] ; [list source [file join $dir tls.tcl] ]
+
Index: Makefile
===
RCS file: /cvs/ports/x11/bwidget/Makefile,v
retrieving revision 1.2
diff -u -d -r1.2 Makefile
--- Makefile9 May 2008 11:31:10 - 1.2
+++ Makefile13 Jul 2008 19:59:32 -
@@ -6,7 +6,7 @@
V= 1.8.0
DISTNAME= BWidget-$V
-PKGNAME= bwidget-$V
+PKGNAME= bwidget-$Vp0
CATEGORIES=x11 x11/tk
HOMEPAGE= http://sourceforge.net/projects/tcllib/
@@ -19,7 +19,7 @@
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=tcllib/}
-RUN_DEPENDS= :tk-8.4*:x11/tk/8.4
+RUN_DEPENDS= :tk-8.5*:x11/tk/8.5
NO_BUILD= Yes
NO_REGRESS=Yes
NEW net/tkabber
Hello, [EMAIL PROTECTED] Here is a nice jabber client. From pkg/DESCR: Tkabber is a free and Open Source client for the Jabber instant messaging system. It's written in Tcl/Tk, and works on many platforms. Tkabber is fully-featured Jabber client. For the full list of features see http://tkabber.jabber.ru/files/doc/tkabber.html#s.features Works on i386 (and on any other arch I think because of Tcl/Tk). No build required. tkabber-0.11.0.tar.gz Description: application/tar-gz
