GNOME 2.20 release notes can be found at
http://www.gnome.org/start/2.20/notes/en/ . Beyond that, this update
includes the new GIMP 2.4 (courtesy of ahze).
The GNOME 2.20 update also includes a huge change in the FreeBSD GNOME
hierarchy. We are now using the more standard DATADIR of ${PREFIX}/share
rather than ${PREFIX}/share/gnome. The result is that fewer patches and
hacks are needed to port GNOME components to FreeBSD. This will mean some
user changes may be required, so be sure to read /usr/ports/UPDATING for
more details.
This release and the things we accomplished in it would not have been
possible without mezz's crazy idea to collapse DATADIR, and his persistence
to make it happen successfully. Ahze and pav also deserve thanks for
their work on porting modules and testing the whole ball of wax on
pointyhat (respectively).
The FreeBSD GNOME team would also like to thank our various testers and
contributors:
Yasuda Keisuke
Frank Jahnke
Pawel Worach
Brian Gruber
Franz Klammer
Yuri Pankov
Nick Barkas
Cristian KLEIN
Tony Maher
Scot Hetzel
Martin Matuska (mm)
Benoit Dejean
Martin Wilke (miwi)
(And anyone else I may have missed)
PRs fixed in this release:
111272, 113470, 115995, 116338
- Add significantly better support in bsd.python.mk for working with
Python Eggs and the easy_install system
Tested by: pointyhat runs
Approved by: pav (portmgr)
Most work by: perky
Thanks to: pav
Note that these directories are be removed by other dependency ports,
so I do not bump PORTREVISION for them. These affected ports are
belong to ports@.
PR: ports/101586
Submitted by: Stanislav Sedov <ssedov at mbsd.msk.ru>
and libgdamm. I am assigning this port back to ports@ in hopes that some
GNOME Postgres user will pick it up, and update it to 1.0.
If there's anything gnome@ can do to help facilitate that, please let us know.
With Glom you can design table definitions and the relationships
between them, plus arrange the fields on the screen. You can edit
and search the data in those tables, and specify field values in
terms of other fields. It's as easy as it should be.
The design is loosely based on FileMaker Pro, with the added
advantage of separation between interface and data. Its simple
framework should be enough to implement most database
applications. Without Glom these systems normally consist of lots
of repetitive, unmaintainable code.
Glom-specific data such as the relationship definitions is saved
in the Glom document. Glom re-connects to the database server
when it loads a previous Glom document. The document is in XML
format.
Glom uses the PostgreSQL database backend but it can not edit
databases that it did not create, because it uses only a simple
subset of Postgres functionality.
Submitted by: adamw
