lack of support for mbrtowc() and wcwidth() in libc [1]
- Mark UTF8 option as EXPERIMENTAL since it seems to don't work so good
in some cases
PR: ports/97862 [1]
Submitted by: Dan Lukes <dan@obluda.cz> [1]
x11-toolkits/gtk--2-reference -> x11-toolkits/gtkmm20-reference
Rename this ports to use the real vendor package name. The advantage of this
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
As for other ports, chase the rename.
PR: ports/97985
Repocopy by: marcus
- 'make test' still fails the same tests as v1.04 (bug report filed with
vendor)
Approved by: tobez (implicit)
1.05 2006-05-26-08-22
- release version 1.05
- added test for auto_purge_on_get
- fixed infinite loop with auto_purge_on_get
- fixed directory paths on Windows partitions
- NullCache uses BaseCache
the communication over the pthread manager pipe a little more robust by
retrying after EINTR failures. Without this fix, linuxthreads based
binaries that run fine on FreeBSD 4 starts crashing in mysterious ways
on FreeBSD 6.
Rename this ports to use the real vendor package name. The advantage of this
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
As for x11-toolkits/py-gnome2, chase the rename.
Rename this ports to use the real vendor package name. The advantage of this
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
As for other ports, chase the rename.
PR: ports/97985
Repocopy by: marcus
Rename this ports to use the real vendor package name. The advantage of this
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
As for other ports, chase the rename.
Rename this ports to use the real vendor package name. The advantage of this
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
PR: ports/97985
Repocopy by: marcus
Rename this ports to use the real vendor package name. The advantage of this
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
As for x11/gnome2 chase the rename.
PR: ports/97985
Repocopy by: marcus
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
As for deskutils/superswitcher, devel/configgen and devel/gnome2-hacker-tools,
chase the rename.
PR: ports/97985
Repocopy by: marcus
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
PR: ports/97985
Repocopy by: marcus
Ruby on Rails framework.
The goal of this project is to provide Rails developers
with everything they need to develop, manage,
test and deploy their applications.
Features include source control, debugging, WEBrick servers,
generator wizards, syntax highlighting, data tools and much much more.
The RadRails IDE is built on the Eclipse RCP, and includes the
Subclipse plug-in and the RDT plug-ins.
The RadRails tools are also available as Eclipse plug-ins.
WWW: http://www.radrails.org/
Submitted by: Alexander Novitsky