Date: Wed, 04 Jan 2006 00:32:37 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Jerzy Gurycz <Jerzy.Gurycz@enarxe.com> Cc: freebsd-emulation@freebsd.org Subject: Re: broken port linux-gtk2-2.4.14_2 Message-ID: <20060104003237.2ipmr151wo040kgc@netchild.homeip.net> In-Reply-To: <43B87182.1090901@enarxe.com> References: <43B87182.1090901@enarxe.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jerzy Gurycz <Jerzy.Gurycz@enarxe.com> wrote: > * <http://cvsweb.FreeBSD.org/ports/x11-toolkits/linux-gtk2>*Sorry if > this is not the standard way to report problems with ports. > If you point me to info on how to do it properly I would do it > (filling some PR form? sending a patch?). A good way to report problems is to send a PR (in case there's no maintainer, it's the only way with some kind of success probability), either with a web browser on the FreeBSD.org site, or with the send-pr command line utility (in case your FreeBSD box has a working mail setup). Ideally the PR comes with a patch which fixes the problem. In this case it's enough to just tell the maintainer (the emulation mailing list) about the name change. I can't fix the port tonight (insufficient computing resources ATM), but I try to get some time tomorrow ("today" actually) in case no other committer fixes the port before I get time to do it. Thanks, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 Grabel's Law: 2 is not equal to 3 -- not even for large values of 2.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060104003237.2ipmr151wo040kgc>