From owner-freebsd-ports@FreeBSD.ORG  Thu Aug 28 14:43:13 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EF44216A4BF
	for <ports@FreeBSD.org>; Thu, 28 Aug 2003 14:43:13 -0700 (PDT)
Received: from planet.krakow.homeunix.com (p19.classcom.pl [62.233.208.19])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A191A43FE0
	for <ports@FreeBSD.org>; Thu, 28 Aug 2003 14:43:12 -0700 (PDT)
	(envelope-from kuba@krakow.homeunix.com)
Received: from planet.krakow.homeunix.com (kuba@localhost [127.0.0.1])
	h7SNkM7r022431;	Fri, 29 Aug 2003 01:46:22 +0200
Received: (from kuba@localhost)h7SNkLs4022429;
	Fri, 29 Aug 2003 01:46:21 +0200
Date: Fri, 29 Aug 2003 01:46:21 +0200
From: Kuba Lida <kuba@krakow.homeunix.com>
Message-Id: <200308282346.h7SNkLs4022429@planet.krakow.homeunix.com>
To: Seth Kingsley <sethk@meowfishies.com>
cc: ports@FreeBSD.org
cc: stolz@i2.informatik.rwth-aachen.de
cc: Stolz@krakow.homeunix.com
cc: Volker@krakow.homeunix.com
Subject: FreeBSD Port: ymessenger-0.99.19.1,20020902;
	broken on 5.1-RELEASE (2)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2003 21:43:14 -0000

Thank you for your almost immediate reply :) I anticipated that it wouldn't be
so easy... if it was I would have found some solution in news groups or
somewhere else.

As to the solution; couldn't the libglib from 4.x be put as, say, a
"compatibility-port" into the port system? And the ymessenger "told" somehow
to use the old libglib, not the one from 5.x? Or couldn't the library be put
right into one of ymessenger's directories and be packaged together with it?
I know it would be a temporary solution and not an elegant one, but maybe it
would allow people who desperately need ymessenger (I fortunately can do well
without it as for now) to use it in their 5.x systems.

I must stress that I am not a system developer, just a willing-to-help BSD
fan that uses FreeBSD for my work (network administrator) since 4.3 release.
Besides, it was my first time I got into the bug-tracking/tech-detail
discussion:) Thanks.

Kuba Lida
Krakow, Poland
kuba@krakow.homeunix.com
http://administracja.free-bsd.org