GNOME 2.5.2 available for FreeBSD

diff --git a/en/gnome/contact.sgml b/en/gnome/contact.sgml index ca6d5b226c..d7cddcac6b 100644 --- a/en/gnome/contact.sgml +++ b/en/gnome/contact.sgml @@ -1,41 +1,41 @@ - + %gnomeincludes; %includes; ]> &header;

Contacts

Any questions regarding GNOME on FreeBSD should be addressed to the freebsd-gnome mailing list. All FreeBSD GNOME users, as well as those who wish to help improve and maintain GNOME on FreeBSD should feel free to - join. - However, you do not have to subscribe if you just want to - report a problem or ask for help - just send your message + join. + However, you do not have to subscribe if you just want to + report a problem or ask for help - just send your message to &email;@FreeBSD.org.

All relevant discussions should be carried out in the mailing list, unless there is a good reason for contacting one of the developers directly. The following is the list of people involved in the FreeBSD GNOME Project (in alphabetical order):

FreeBSD GNOME developers can also be found lurking on IRC. +

FreeBSD GNOME developers can also be found lurking on IRC. So please join #freebsd-gnome on FreeNode if you would like to discuss GNOME on FreeBSD.

&footer; diff --git a/en/gnome/docs/bugging.sgml b/en/gnome/docs/bugging.sgml index 251bc0a579..51f2191606 100644 --- a/en/gnome/docs/bugging.sgml +++ b/en/gnome/docs/bugging.sgml @@ -1,125 +1,125 @@ - + %gnomeincludes; %includes; ]> &header;

1. What to report?

The rule of the thumb is: report as much information as you - can. Even if there is some irrelevant information - developers can easily filter it out. On the contrary, the - situation is much worse when there is too little information to - reliably track down or reproduce the problem - in this case - developers have to spend their time guessing and/or asking + can. Even if there is some irrelevant information + developers can easily filter it out. On the contrary, the + situation is much worse when there is too little information to + reliably track down or reproduce the problem - in this case + developers have to spend their time guessing and/or asking originator of report to send more information.

There are plenty of examples of totally useless bug reports, - something like "Hey, gnomefoo port is broken. I'm running - FreeBSD-X.Y. Please fix." Needless to say, that such a report - is just a waste of your time, time of the appropriate developer, - and network bandwidth. At a bare minimum the report should +

There are plenty of examples of totally useless bug reports, + something like "Hey, gnomefoo port is broken. I'm running + FreeBSD-X.Y. Please fix." Needless to say, that such a report + is just a waste of your time, time of the appropriate developer, + and network bandwidth. At a bare minimum the report should include the following information:

Exact version of the operating system (usually output of uname -a).
List of all packages installed on your system.
Your environment (output of /usr/bin/env). -
If you are building from ports then the approximate time +
If you are building from ports then the approximate time when you last updated your ports tree.
Information specific for each type of breakage: full log of - unsuccessful build in the case when the build of the port is - broken, stack trace in the case of a core dump, clear and - detailed description of the problem when the application does - something unexpected, etc. Try to put yourself into the - developer's shoes and in each particular case evaluate what - information would be necessary for them to locate the source of - the problem. Do not just assume that they already know all + unsuccessful build in the case when the build of the port is + broken, stack trace in the case of a core dump, clear and + detailed description of the problem when the application does + something unexpected, etc. Try to put yourself into the + developer's shoes and in each particular case evaluate what + information would be necessary for them to locate the source of + the problem. Do not just assume that they already know all about the problem, but are just too lazy to fix it.

In addition, try to answer the following questions:

What exactly is the problem? : Explain the problem as clearly and precisely as possible. Try to limit the actual problem description to one or two key sentences.
Where is the problem occurring? : Include whether or not you are seeing the problem during compile-time, install-time, or run-time. Also mention what machine (maybe you have multiple) and in what locale (i.e. the value of the LANG environment variable) the problem is occurring.
When did the problem first occur? : Try to isolate exactly when the problem started to occur. If this never worked, or you always had a problem, say that, too. Also mention when last the problem was observed, as well as when last things were working as expected (if applicable).
What is the magnitude of this problem? : Explain if the problem is getting worse, getting better, or staying the same. We realize many problems "just are," but this type of information can be helpful in certain cicumstances.

Also, be prepared to answer additional questions. Often times, developers cannot solve or even diagnose a problem right off the bat. So please be understanding when asked to provide more information.

If you have a solution or a workaround for the problem then include - it into your report as well, even if you are not quite sure that - this is a correct fix. If it is not it could still give the + it into your report as well, even if you are not quite sure that + this is a correct fix. If it is not it could still give the developer an idea about what to look at; and save them some time.

2. Where to report?

Before reporting a bug, or even sending an email to the list, search through the FreeBSD GNOME mailing list archives to see if this has already been reported. Most of the problems reported on the mailing list are repeats, and by searching you can find your solution much faster.

Once you are sure this is a new problem, there are several ways - to report a bug in GNOME running on FreeBSD: you could +

Once you are sure this is a new problem, there are several ways + to report a bug in GNOME running on FreeBSD: you could send a report to the freebsd-gnome mailing list, file a problem report in the FreeBSD bug reporting system, send your report to the particular GNOME developers via their - bug tracking system, or + bug tracking system, or any combination of those.

It is impossible to define guidelines that will clearly tell you - where to report in each particular case - you have to use your own +

It is impossible to define guidelines that will clearly tell you + where to report in each particular case - you have to use your own common sense, however some rules follow:

If the problem is FreeBSD-specific and transient (e.g. - checksum mismatch, patch failure, syntax error in port's Makefile +
If the problem is FreeBSD-specific and transient (e.g. + checksum mismatch, patch failure, syntax error in port's Makefile etc.) then report to the freebsd-gnome mailing list.
If the problem is clearly not FreeBSD-specific and you have +
If the problem is clearly not FreeBSD-specific and you have no readily available solution then report to the developers of the - software directly (for most core GNOME components this means that + software directly (for most core GNOME components this means that you need to use their Bugzilla bug tracking system).
If the problem is not FreeBSD-specific, but quite serious - and you have a fix available then report both to FreeBSD and - author's bug tracking systems, so that the appropriate port will - be patched and other users of FreeBSD will be able to benefit - from your fix, without the need to wait for the vendor's next +
If the problem is not FreeBSD-specific, but quite serious + and you have a fix available then report both to FreeBSD and + author's bug tracking systems, so that the appropriate port will + be patched and other users of FreeBSD will be able to benefit + from your fix, without the need to wait for the vendor's next release.

&footer; diff --git a/en/gnome/docs/faq2.sgml b/en/gnome/docs/faq2.sgml index fb3b8d7eaf..66f4a37fc5 100644 --- a/en/gnome/docs/faq2.sgml +++ b/en/gnome/docs/faq2.sgml @@ -1,646 +1,646 @@ - + %gnomeincludes; %includes; ]> &header;

How do I get GNOME &gnomever; for FreeBSD? -
GNOME &gnomever; is failing to build from ports. What +
GNOME &gnomever; is failing to build from ports. What do I do? -
I installed GNOME &gnomever;, but I am missing +
I installed GNOME &gnomever;, but I am missing application foo. What gives?
What is the best way to upgrade from GNOME 1.4 to GNOME 2?
What is the best way to upgrade from GNOME 2.2 to GNOME &gnomever;? -
How do I keep my GNOME &gnomever; components +
How do I keep my GNOME &gnomever; components and applications up-to-date?
Can I install GNOME 1.4 applications under GNOME &gnomever;?
Where can I get more themes for GNOME &gnomever;?
What window managers work well with GNOME &gnomever;?
Does GNOME &gnomever; support anti-aliased fonts?
How can I control what fonts are anti-aliased?
How do I edit my GNOME 2 menus? -
How do I use GTK+ 2 resource settings for +
How do I use GTK+ 2 resource settings for GTK+ 2 applications when not in a GNOME environment?
How do I configure settings for GNOME 1.4 applications under GNOME &gnomever;?
Nautilus-cd-burner does not let me burn CDs. How can I fix this?
How do I add new GDM sessions?

Full Text

How do I get GNOME &gnomever; for FreeBSD?
-
There are two ways to install GNOME &gnomever; on FreeBSD. One way is to use +
There are two ways to install GNOME &gnomever; on FreeBSD. One way is to use packages, and the other way is to use ports. Before doing either installation, you should first familiarize yourself with the GNOME &gnomever; release notes.

To install GNOME &gnomever; from packages, use the command:
# pkg_add -r gnome2 -
This will download the latest GNOME &gnomever; packages from the +
This will download the latest GNOME &gnomever; packages from the FreeBSD FTP site, and proceed to install them on your system.
-
To build and install GNOME &gnomever; from ports, you should first +
To build and install GNOME &gnomever; from ports, you should first cvsup the latest ports tree. Then:
```
 # cd /usr/ports/x11/gnome2
 # make clean
 # make install clean
 	    
```
For the best GNOME &gnomever; experience, you should install from - ports, after adding the following macros to your + ports, after adding the following macros to your /etc/make.conf file:
```
 WITH_FAM=	yes
 WITH_LAME=	yes
 	    
```
WITH_FAM enables file alteration manager support which allows Nautilus to update its file lists in real-time as well as allows all GNOME components to detect config file changes without needing to restart GNOME. Note that for FAM to work properly, you also need to add the following to /etc/rc.conf then reboot:

For FreeBSD 4.x:
portmap_enable="YES"

For FreeBSD 5.x:
rpcbind_enable="YES"

If you install GNOME from packages, or you build it from ports without FAM enabled, all you need to do to enable FAM support is rebuild devel/gnomevfs2 after adding WITH_FAM to /etc/make.conf.

WITH_LAME adds MP3 support, enabling you to play MP3s directly in Nautilus. If you install GNOME from packages or build it from ports without LAME support enabled, all you need to do to enable LAME support is rebuild multimedia/nautilus-media after adding WITH_LAME to /etc/make.conf.

These options may cause build errors on certain platforms, and thus they are not enabled by default.

Once you have the GNOME &gnomever; desktop installed, GNOME &gnomever; can be started by adding the following line to ~/.xsession or ~/.xinitrc, as appropriate:
```
 exec gnome-session
 	    
```
GNOME &gnomever; is failing to build from ports. What do I do?
-
The majority of GNOME &gnomever; compilation problems can be solved - by making sure all the necessary GNOME &gnomever; components are +
The majority of GNOME &gnomever; compilation problems can be solved + by making sure all the necessary GNOME &gnomever; components are up-to-date.
- +
In general, when a GNOME &gnomever; component is not up-to-date, you will see an error similar to the following:
```
 checking for libgnomeui-2.0 libbonoboui-2.0 libbonobo-2.0 >= 2.2.1
-gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2 libglade-2.0... 
+gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2 libglade-2.0...
 configure: error: Library requirements (libgnomeui-2.0 libbonoboui-2.0
 libbonobo-2.0 >= 2.2.1 gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2
 libglade-2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable
 if your libraries are in a nonstandard prefix so pkg-config can find them.
 	      
```
- +
Simply keeping your ports tree up-to-date will prevent these errors.
- +
If the pkg-config program is out-of-date, you may see a configure error similar to the following:
```
 configure: error: *** pkg-config too old; version 0.14 or better required.
 	      
```
While this may be buried in some other text, the error is very straight-forward: you need to upgrade pkg-config. - The pkg-config application is found in the + The pkg-config application is found in the devel/pkgconfig port. By updating this port to the latest version, this error will go away.
- -
You may see compiler errors relating to pthreads + +
You may see compiler errors relating to pthreads (&posix; threads), such as:
```
 undefined reference to 'strerror_r'
             
```
To fix thread related errors, make sure you have the following compiled into your kernel:
```
 options     _KPOSIX_PRIORITY_SCHEDULING
             
```
If you are tracking -stable or -current, make sure that you - do not have NOLIBC_R set in + do not have NOLIBC_R set in /etc/make.conf. If you do, remove it, then rebuild world. - If you still have trouble, please send email to + If you still have trouble, please send email to &email;@FreeBSD.org with the output of the failed compilation. It is also helpful to include the config.log from the port's work directory.

Ports such as devel/pth and devel/ngpt can also cause pthread-related problems when compiling GNOME &gnomever;. If you do not need these ports installed, it is recommended that you remove them.

A common source of build failures is the existence of multiple versions of the same library. This can happen if you have two different versions of a port installed, or can even happen through normal portupgrade use. You can back up the libraries in /usr/local/lib/compat/pkg and remove them, and then run portupgrade -u -rf pkgconfig. This will force a rebuild of all GNOME-related apps (and a fair number of other apps) without retaining old versions of libraries in /usr/local/lib/compat/pkg.
I installed GNOME &gnomever;, but I am missing application foo. What gives?

Only the core desktop is included in the gnome2 package. Here are some other GNOME - meta-ports that offer convenient groupings of popular GNOME 2 + meta-ports that offer convenient groupings of popular GNOME 2 software.
- +
- The GNOME 2 Fifth Toe (x11/gnome2-fifth-toe) consists of stable GNOME 2 applications that many users expect to find in a functional desktop environment. This includes image manipulation applications, chat and instant messenger applications, and music and multimedia players
- The GNOME 2 Hacker Tools - (devel/gnome2-hacker-tools) consists of applications - developers would need to create and maintain GNOME software - projects. This includes IDEs, interface builders, ``hacker'' + (devel/gnome2-hacker-tools) consists of applications + developers would need to create and maintain GNOME software + projects. This includes IDEs, interface builders, ``hacker'' editors, and code generation tools.
- The GNOME 2 Office (editors/gnome2-office) +
- The GNOME 2 Office (editors/gnome2-office) consists of applications that are commonly found in office or productivity suites. This includes a spreadsheet application, word processor, project management application, database access application, groupware suite, and diagramming application.
To install any of these from packages:
```
 # pkg_add -r meta-port
             
```
For example, to install the GNOME 2 Fifth Toe from packages:
- +
```
 # pkg_add -r gnome2-fifth-toe
 	    
```
To install any of these from ports:
```
 # cd /usr/ports/category/meta-port
 # make clean
 # make install clean
 	    
```
For example, to install the GNOME 2 Fifth Toe from ports:
```
 # cd /usr/ports/x11/gnome2-fifth-toe
 # make clean
 # make install clean
 	    
```
What is the best way to upgrade from GNOME 1.4 to GNOME 2?

If you have GNOME 1.4, and you want to upgrade to GNOME &gnomever;, first familiarize yourself with the official upgrade instructions from the GNOME site. Make sure your GNOME 1.4 ports are up-to-date, and then remove the following GNOME 1.4 packages from the system:
- +
```
 gnomecore
 sawfish
-gnomeapplets 
+gnomeapplets
 gnomemedia
 gtop
 libgtop
 nautilus
 gedit
 xalf
 bugbuddy
 gnomeaudio
 gnomegames
 gnomeutils
 gdm
 eog
 ggv
 	   
```
-
After those packages are removed, you can build GNOME &gnomever; as per +
After those packages are removed, you can build GNOME &gnomever; as per the instructions listed above.

What is the best way to upgrade from GNOME 2.2 to GNOME &gnomever;?

We recommend that you use /usr/ports/sysutils/portupgrade for this purpose. The following will do the job well:

 # pkgdb -F
 (answer yes to all prompts; note that you might wish
 to run the above command after each step below)
 # portupgrade ORBit2 libbonobo
 # portupgrade -rf -m BATCH=yes atk
 # portupgrade -R -m BATCH=yes gnome2

-
How do I keep my GNOME &gnomever; components and applications +
How do I keep my GNOME &gnomever; components and applications up-to-date?

You are emphatically encouraged to use portupgrade -- and only portupgrade -- to keep your GNOME &gnomever; components and applications up-to-date.

Once you have updated your ports tree (presumably with cvsup), the following two simple commands will update what needs to be updated, and will prevent inconsistencies:

# pkgdb -F # portupgrade -a

Despite consistent utilization of portupgrade, if it seems like everything is refusing to build with everything else, you might save yourself a headache or three by removing all your GNOME apps and reinstalling them (your data files will remain untouched). To do this, follow these commands:

# pkgdb -F # pkg_delete -rf pkgconfig\* # cd /usr/ports/x11/gnome2 # make clean # make install clean

After running the above commands, you will have to reinstall all the GNOME applications you desire. This process sounds painful, but it is actually a great way to clear cruft off of your system. Just install applications as you need them, and you'll be surprised how much disk space you have reclaimed. A full rebuild does take a significant amount of time; fortunately, this measure is only rarely needed.

Can I install GNOME 1.4 applications under GNOME &gnomever;?

GNOME 1.4 ports will run well under the GNOME 2 desktop. Older applications that were incompatible with the GNOME 2 desktop have been removed from the ports tree, so it should be safe to run any GNOME application in the ports tree under the GNOME 2 desktop.

Where can I get more themes for GNOME &gnomever;?
-
The website +
The website art.gnome.org has been setup as a general GNOME theme repository. They offer some gtk+-2, metacity, sawfish, nautilus, icon, and gdm themes, as well as some backgrounds.

A new theme site called The Theme Depot has just been launched. This site contains themes for GNOME 2 as well as KDE and quite a few window managers.
- +
Freshmeat.net has a themes archive at themes.freshmeat.net, which contains themes and backgrounds for many window managers, theme engines, and desktop environments. This site grew out of the old themes.org.

A good site for some cool GNOME icons (some stock, some new) - is jimmac's + is jimmac's Icons site.

See the instructions on the website for installing the themes. If you feel inclined to port a few of them, you will not be turned away ;-).

What window managers work well with GNOME &gnomever;?
-
The gnome2 meta-port installs the +
The gnome2 meta-port installs the metacity window manager by default. Another popular window - manager that works well with GNOME &gnomever; is + manager that works well with GNOME &gnomever; is sawfish. Sawfish can be found in x11-wm/sawfish2.

To switch between metacity and sawfish in GNOME 2, you will need to do the following:

killall metacity; sawfish & gnome-session-save --gui

The gnome-session-save is important. Without it, the window manager will revert back to the one previously configured - upon next login. To switch back, simply reverse sawfish and + upon next login. To switch back, simply reverse sawfish and metacity.

If you have gotten the GNOME &gnomever; desktop working under an alternative window manager, please take a screenshot and send it to us!

Does GNOME &gnomever; support anti-aliased fonts?
-
Yes! Anti-aliasing requires XFree86 4.x with +
Yes! Anti-aliasing requires XFree86 4.x with freetype2 support. To add freetype2 support to X, make - sure you have the following modules loaded in your + sure you have the following modules loaded in your XF86Config file under the Modules section:

Load "freetype" Load "type1"
- +
Then, simply check out the Fonts capplet under Applications->Desktop Preferences. If you want a good set - of TrueType starter fonts, install the + of TrueType starter fonts, install the x11-fonts/webfonts port.

Sometimes, after adding new fonts to the system, it is necessary to teach fontconfig about them. If you find that - newly added fonts are not made available even after + newly added fonts are not made available even after restarting GNOME 2, run the following command as root:

# fc-cache -f -v
-
If you have any questions, please send them to +
If you have any questions, please send them to &email;@FreeBSD.org.

How can I control what fonts are anti-aliased?
-
GNOME &gnomever; makes use of Xft and fontconfig to handle +
GNOME &gnomever; makes use of Xft and fontconfig to handle anti-aliasing. Fontconfig is a very powerful XML-based font configuration package. You can create a ~/.fonts.conf file that controls virtually every aspect of fontconfig. For example, if you do not want to anti-alias fonts smaller than 16 point, create a ~/.fonts.conf with the following contents:

<?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <match target="font"> <test name="size" compare="less_eq"> <double>16</double> </test> <edit name="antialias" mode="assign"> <bool>false</bool> </edit> </match> </fontconfig>

Refer to fonts-conf(5) for more information.

How do I edit my GNOME 2 menus?

You need to use Nautilus to edit your GNOME 2 menus. If you want to edit any menu other than Favorites, you must be root.
-
To edit the menus, launch Nautilus, and enter the URL +
To edit the menus, launch Nautilus, and enter the URL applications:///. From there you should be able to edit your entire application menu.

How do I use GTK+ 2 resource settings for GTK+ 2 applications when not in a GNOME environment?

GNOME 2 applications get their GTK+ 2 resources from themes and the corresponding theme engine. If you would rather run your GTK+ 2 applications in a non-GNOME environment then you will need to create a file named ~/.gtkrc-2.0.

To use the widgets from a GTK+ 2 theme when in a non-GNOME environment, simply include the theme's gtk-2.0/gtkrc in your ~/.gtkrc-2.0. For example:
include "/usr/X11R6/share/themes/Crux/gtk-2.0/gtkrc"

If you prefer, you can use the same GTK+ 1.2 theme for both GTK+ 1.2 and GTK+ 2 applications, which will give your GTK+ programs a consistent look. For the most part, you can transfer your settings from your ~/.gtkrc file (used for GTK+ 1.2) with a couple of caveats.

If you have any theme engine references, you will have - to make sure there is a corresponding GTK+ 2 theme engine. + to make sure there is a corresponding GTK+ 2 theme engine. Otherwise, remove the engine entries.

The default font specification should be outside of any style blocks and should be specified with the gtk-font-name keyword. For example:
gtk-font-name = "Verdana 11"

Note that while a GTK+ 1.2 gtkrc file will work in a GTK+ 2 gtkrc-2.0 file, the opposite is not true: the contents of a GTK+ 2 gtkrc-2.0 file will not work inside a GTK+ 1.2 gtkrc file.

How do I configure settings for GNOME 1.4 applications under GNOME &gnomever;?

Install sysutils/gnomecontrolcenter, then invoke gnomecc from the command line to bring up the GNOME 1.4 control center.

Nautilus-cd-burner does not let me burn CDs. How can I fix this?

Nautilus-cd-burner cannot write to CD/DVD burners unless support for those devices is enabled in the kernel, and the permissions on the device nodes allow write access. Nautilus-cd-burner talks to CD/DVD burners through the SCSI CAM subsystem. Therefore, you must make sure - you have the following configured in your kernel:
+ you have the following configured in your kernel:

device scbus device cd device pass

You must also make sure you have the following configured in your kernel if you are using an ATAPI CD/DVD burner:

device atapicam

To figure out which CD/DVD drive you will be using, run the following command as root:

# camcontrol devlist

Your output will look similar to the following:

<QSI CDRW/DVD SBW-242 UD22> at scbus1 target 0 lun 0 (cd0,pass0)

The devices in parentheses at the end are important. You must make sure the /dev entries for those devices - are writable by the users that will be using + are writable by the users that will be using nautilus-cd-burner. In addition to those devices, - /dev/xpt* must also be writable to your - nautilus-cd-burner users. The following + /dev/xpt* must also be writable to your + nautilus-cd-burner users. The following /etc/devfs.conf configuration will achieve the - desired results given the above devlist (NB: + desired results given the above devlist (NB: devfs.conf is only supported on FreeBSD 5.x):

perm cd0 0666 perm xpt0 0666 perm pass0 0666

On FreeBSD 4.x, you can simply set the device node permissions, and they will be preserved across reboots. Note that you must use the 'c' device nodes on FreeBSD 4.x (e.g. cd0c).

How do I add new GDM sessions?

The process for adding new GDM sessions has changed substantially between GNOME 2.2 and &gnomever;. In order to add new sessions now, you must create a .desktop file containing the session configuration information. Session files live in /usr/X11R6/etc/dm/Sessions. For example, to add a KDE session, create a file in /usr/X11R6/etc/dm/Sessions called kde.desktop. That file should contain the following:

[Desktop Entry] Encoding=UTF-8 Name=KDE Comment=This session logs you into KDE Exec=/usr/local/bin/startkde TryExec=/usr/local/bin/startkde Icon= Type=Application

This file must have execute permissions. For example:

# chmod 0555 kde.desktop

After creating this file, restart GDM, and there will be a KDE link under the Sessions menu.

&footer; diff --git a/en/gnome/docs/gnome2_porting.sgml b/en/gnome/docs/gnome2_porting.sgml index 67bd6be72f..4ef314870a 100644 --- a/en/gnome/docs/gnome2_porting.sgml +++ b/en/gnome/docs/gnome2_porting.sgml @@ -1,268 +1,268 @@ - + %gnomeincludes; %includes; ]> &header;
To see how to utilize these components, please examine the example Makefile.
- + - + - + - + - + - + - + - + - + - +

COMPONENT ASSOCIATED PROGRAM IMPLIED COMPONENTS

atk devel/atk glib20

atspi x11-toolkits/at-spi gail libbonobo

eel2 x11-toolkits/eel2 gnomevfs2 libgnomeui gail

gail x11-toolkits/gail libgnomecanvas

gal2 x11-toolkits/gal2 gnomeui libgnomeprintui

gconf2 devel/gconf2 orbit2 libxml2 gtk20 linc

glib20 devel/glib20 gnometarget pkgconfig

gnomecontrolcenter2 sysutils/gnomecontrolcenter2 gnomedesktop metacity nautilus2

gnomedesktop x11/gnomedesktop libgnomeui

gnomepanel x11/gnomepanel libwnck gnomedesktop

gnomevfs2 devel/gnomevfs2 gconf2 libbonobo gnomemimedata

gtk20 x11-toolkits/gtk20 atk pango
gtksourceview x11-toolkits/gtksourceview libgnome libgnomeprintui
libartlgpl2 graphics/libartlgpl2 pkgconfig

libbonobo devel/libbonobo libxml2 orbit2
libbonoboui x11-toolkits/libbonoboui libgnomecanvas libgnome

libgailgnome x11-toolkits/libgail-gnome libgnomeui atspi

libgda2 databases/libgda2 glib20 libxslt

libglade2 devel/libglade2 libxml2 gtk20
libgnome x11/libgnome libxslt gnomevfs2 esound

libgnomeui x11-toolkits/libgnomeui libbonoboui

libgnomecanvas graphics/libgnomecanvas libglade2 libartlgpl2

libgnomedb databases/libgnomedb libgnomeui libgda2

libgnomeprint print/libgnomeprint libbonobo libartlgpl2 gtk20

libgnomeprintui x11-toolkits/libgnomeprintui libgnomeprint libgnomecanvas

libgsf devel/libgsf gnomevfs2 libbonobo

libgtkhtml www/libgtkhtml libxslt gnomevfs2 gail

libidl devel/libIDL glib20
libwnck x11-toolkits/libwnck gtk20

librsvg2 graphics/librsvg2 gtk20 libgsf

libxml2 textproc/libxml2 pkgconfig
libxslt textproc/libxslt libxml2
libzvt x11-toolkits/libzvt gtk20

linc net/linc glib20
nautilus2 x11-fm/nautilus librsvg2 eel2 gnomedesktop

metacity x11-wm/metacity gconf2 glade2

orbit2 devel/ORBit2 libidl
pango x11-toolkits/pango glib20
vte x11-toolkits/vte gtk20

If you still need help with your port, have a look at some of the existing ports for examples. The freebsd-gnome mailing list is also there for you.
&footer; diff --git a/en/gnome/docs/gnome_porting.sgml b/en/gnome/docs/gnome_porting.sgml index f04fae12e4..e387eff246 100644 --- a/en/gnome/docs/gnome_porting.sgml +++ b/en/gnome/docs/gnome_porting.sgml @@ -1,112 +1,112 @@ - + %gnomeincludes; %includes; ]> &header;
To see how to utilize these components, please examine the example Makefile.

COMPONENT ASSOCIATED PROGRAM IMPLIED COMPONENTS

esound audio/esound

gnomehack gnomehack makes common GNOME Makefile substitutions that nearly every GNOME port requires to fit into the proper mtree structure. Note: Including this option adds a pre-patch target to your Makefile. Therefore, only explicitly define post-patch.

gnomehier gnomehier installs all the - directories needed for both the GNOME 1 and 2 desktops. + directories needed for both the GNOME 1 and 2 desktops. Only include this option if your port calls @dirrm on one of the directories listed in the plist for gnomehier.

gnomemimedata misc/gnomemimedata gnomehier pkgconfig

gnomeprefix gnomeprefix sets some CONFIGURE_ARGS to ensure data is placed properly within the GNOME hierarchy. gnomehier

gnometarget gnometarget sets ${CONFIGURE_TARGET} for ports whose configure script does not figure it out automatically.

intlhack intlhack registers a dependency upon textproc/intltool and patches broken intltool-merge.in implementations. NOTE: Only available for the GNOME &gnomedevelver; tree.

lthack lthack prevents the installation of .la files and ensures that ${PTHREAD_LIBS} will be passed to the linker. NOTE: Only available for the GNOME &gnomedevelver; tree.

pkgconfig pkgconfig registers a dependency upon devel/pkgconfig to make sure it is installed.

If you still need help with your port, have a look at some of the existing ports for examples. The freebsd-gnome mailing list is also there for you.
&footer; diff --git a/en/gnome/docs/knownissues.sgml b/en/gnome/docs/knownissues.sgml index fef1b5868c..2bf466f609 100644 --- a/en/gnome/docs/knownissues.sgml +++ b/en/gnome/docs/knownissues.sgml @@ -1,74 +1,74 @@ - + %gnomeincludes; %includes; ]> &header; -
Below is a list of known issues with GNOME &gnomever; that are +
Below is a list of known issues with GNOME &gnomever; that are specific to FreeBSD. These are not the only known issues, however. Please familiarize yourself with the GNOME &gnomever; - release notes which contains a + release notes which contains a list of known issues that affect all platforms.

1. Upgrading from GNOME 2.2 to &gnomever; is tricky

You should follow the instructions for updating to GNOME &gnomever;. This may still produce errors, however. You may have to re-run - pkgdb -F after each step. If you continue to + pkgdb -F after each step. If you continue to encounter errors after following the upgrade instructions, log the entire upgrade procedure (you can use the -l - option to portupgrade to accomplish this). - Compress and send the log to + option to portupgrade to accomplish this). + Compress and send the log to &email;@FreeBSD.org.

2. evolution has a problem with attachments under GNOME &gnomever;

evolution-1.4.4 has a problem with attachments under GNOME &gnomever;. To work around the problem, do the following, as root:

# ln -s /usr/X11R6/share/icons/gnome/48x48/apps/gnome-unknown.png /usr/X11R6/share/gnome/pixmaps/gnome-unknown.png

This problem was fixed in evolution-1.4.5, and upgrading to evolution-1.4.5 is probably the best solution.

3. gstreamer doesn't play nice with rhythmbox

gstreamer-0.6.3 doesn't play nice with rhythmbox. It is recommended you build rhythmbox with -DWITH_XINE for - now. (UPDATE: As of gstreamer-plugins-0.6.3_1, this + now. (UPDATE: As of gstreamer-plugins-0.6.3_1, this problem has been resolved.)

4. GDM crashes on startup

GDM may crash on startup, especially on 5.1-RELEASE and - earlier. All GDM users need to copy + earlier. All GDM users need to copy /usr/X11R6/etc/gdm/factory-gdm.conf over /usr/X11R6/etc/gdm/gdm.conf. The old - config version from GNOME 2.2 will not work. Users of + config version from GNOME 2.2 will not work. Users of 5.1-RELEASE and earlier need to read the pkg-message that comes with the GDM2 port/package on how to patch OpenPAM to work with GDM2.

5. gnomemeeting fails to build

Gnomemeeting may fail to build if you have ffmepg installed. If you do, remove ffmpeg, then build gnomemeeting, then reinstall ffmpeg if so desired.
&footer; diff --git a/en/gnome/docs/porting.sgml b/en/gnome/docs/porting.sgml index c703b0be40..c5c3d1d63b 100644 --- a/en/gnome/docs/porting.sgml +++ b/en/gnome/docs/porting.sgml @@ -1,307 +1,307 @@ - + %gnomeincludes; %includes; ]> &header;
This document assumes that you already know how the port system works, and therefore only provides GNOME-specific hints and tips. General - instructions can be found in the + instructions can be found in the FreeBSD Porter's Handbook.

Example Makefile

There is an example Makefile for a GNOME port, which uses many of the tricks outlined in this document. Please feel free to use it as a guide for creating your own ports.

GNOME Makefile Macros

GNOME applications under FreeBSD use the USE_GNOME infrastructure. To specify which components of the GNOME system your port needs in order to build, simply list them all as a space-separated list. For example:

USE_X_PREFIX= yes USE_GNOME= gnomeprefix gnomehack libgnomeui

The USE_GNOME components are divided into the following two lists:

GNOME desktop-version-independent components

GNOME 2 components

GNOME 1 components

If your port needs only GTK2 libraries, the following is the shortest way to define this:

USE_X_PREFIX= yes USE_GNOME= gtk20

If your port needs only GTK1 libraries, the following is the shortest way to define this:

USE_X_PREFIX= yes USE_GNOME= gtk12

Even if your application needs only the GTK libraries, other USE_GNOME components may be useful. Please scan the entire list to make sure your port uses all relevant components.
-
Once you have finished with your port, it is a good idea to - verify that your port depends on the correct list of components. +
Once you have finished with your port, it is a good idea to + verify that your port depends on the correct list of components. To see a list of what packages your port will actually require, use the command make package-depends from within your port's directory.

To aid in creating the list of necessary components, it can be helpful to examine the output of make configure. At the end of the checking for... list, there will be a line similar to this:

checking for libgnomeui-2.0 >= 2.0.0 cspi-1.0 >= 1.1.7 libspi-1.0 >= 1.1.7 libbonobo-2.0 >= 2.0.0 atk >= 1.0.0 gtk+-2.0 >= 2.0.0 gail libwnck-1.0 esound... yes

This is a list of the components upon which this application relies to build. Pay close attention to the hierarchical layout of the USE_GNOME system; many components are implied from other USE_GNOME directives. In the above example, USE_GNOME= libgnomeui implies use of libbonoboui, which implies libgnomecanvas, which implies libglade2, which implies gtk20. Thus, even though gtk+-2.0 appears in the list of requisite components, gtk20 can be eliminated from the USE_GNOME list. There are a number of other such redundancies that can be eliminated from this list.
-
For the above list (taken from sysutils/gok), the +
For the above list (taken from sysutils/gok), the following is defined in the Makefile:
USE_GNOME= gnomehack gnomeprefix libgnomeui atspi libwnck

GNOME 1 Desktop vs. GNOME 2 Desktop

In the beginning, there was only GNOME 1. When the GNOME 2 desktop came around, maximum backwards compatability was ensured, within reason. GNOME 1 applications can run fine under the GNOME 2 desktop, provided that the applications do not utilize functionality specific to the GNOME 1 desktop environment.

The GNOME 1 desktop, and all applications that will not run under the GNOME 2 desktop, have been removed from the ports tree.

What this means for you, as an application porter, is simply that you should not add GNOME 1-specific applications to the ports tree.
- +
If you wish to determine which version of the GNOME desktop environment is present on a user's machine, you can check the value of GNOME_DESKTOP_VERSION. This variable is set to either "1" or "2" depending upon whether the GNOME 1 or GNOME 2 desktop is installed.

Optional GNOME Dependencies
-
If your port can optionally use GNOME, you must set +
If your port can optionally use GNOME, you must set WANT_GNOME= yes in your Makefile, then check to see if HAVE_GNOME is set for each component from the list above that your port can use. Since this is a conditional evaluation, you need to stick it between bsd.port.pre.mk and bsd.port.post.mk. For example:

WANT_GNOME= yes .include <bsd.port.pre.mk> .if ${HAVE_GNOME:Mgnomepanel}!="" USE_GNOME+= gnomeprefix gnomepanel CONFIGURE_ARGS+= --with-gnome PKGNAMESUFFIX= -gnome PLIST_SUB= DATADIR="share/gnome" .else CONFIGURE_ARGS+= --without-gnome PLIST_SUB= DATADIR="share" .endif .include <bsd.port.post.mk>

Here, WANT_GNOME tells the ports system - to check for the existence of the various GNOME components + to check for the existence of the various GNOME components listed above. For each component found, its name is appended - to HAVE_GNOME. Since this port can use gnomepanel, - we check HAVE_GNOME to see if it contains - gnomepanel (for more on the :Mpattern make syntax, - please refer to the + to HAVE_GNOME. Since this port can use gnomepanel, + we check HAVE_GNOME to see if it contains + gnomepanel (for more on the :Mpattern make syntax, + please refer to the make(1) manpage). If gnomepanel is found, then it is added the list of - USE_GNOME dependencies, and the port-specific + USE_GNOME dependencies, and the port-specific --with-gnome CONFIGURE_ARG is passed. In an old GNOME infrastructure, PKGNAMESUFFIX was automatically adjusted by the proper USE_* macro. Now it is up to the individual porter to do this. Our example port appends -gnome to the port name - to indicate it has been built with GNOME support. The same is - true for the DATADIR PLIST_SUB. The + to indicate it has been built with GNOME support. The same is + true for the DATADIR PLIST_SUB. The individual porter must decide when do the DATADIR substitution. A good rule of thumb is to add the DATADIR PLIST_SUB when using the gnomeprefix - component. + component.
-
Note: You cannot add extra default USE_GNOME +
Note: You cannot add extra default USE_GNOME components after the .include <bsd.port.pre.mk>. That is, the following is wrong :

.include <bsd.port.pre.mk> .if ${HAVE_GNOME:Mgnomelibs}!="" USE_GNOME+= libgnome .else USE_GNOME+= gtk12 # WRONG! .endif

This will make the build system think that GNOME is desired, and mark the pkg-plist accordingly, thus breaking package builds. If you need to add default USE_GNOME components, do so above the .include <bsd.port.pre.mk> line.

To enforce use of optional GNOME dependencies unconditionally, you can add WITH_GNOME= yes to /etc/make.conf or on the make command line. This will always return true when checking for optional GNOME dependencies. If you want the system to always return false when checking for optional GNOME dependencies, you can add WITHOUT_GNOME= yes to /etc/make.conf or to the make command line.

More information on the USE_GNOME infrastructure can be found by looking at the source and comments of ${PORTSDIR}/Mk/bsd.gnome.mk.

OMF Installation

A large number of GNOME applications (especially GNOME 2 applications) install Open Source Metadata Framework (OMF) - files which contain the help file information for those - applications. These OMF files require special processing + files which contain the help file information for those + applications. These OMF files require special processing by ScrollKeeper in order for applications like Yelp to - find help documentation. In order to accomplish proper + find help documentation. In order to accomplish proper registry of these OMF files when installing GNOME applications - from packages, you should make sure your port's - pkg-plist has the following for each OMF file + from packages, you should make sure your port's + pkg-plist has the following for each OMF file listed.

@exec scrollkeeper-install -q \ %D/path/to/help_file.omf \ 2>/dev/null || /usr/bin/true @unexec scrollkeeper-uninstall -q \ %D/path/to/help_file.omf \ 2>/dev/null || /usr/bin/true

For example:

@exec scrollkeeper-install -q \ %D/share/gnome/bug-buddy/bug-buddy-C.omf \ 2>/dev/null || /usr/bin/true @unexec scrollkeeper-uninstall -q \ %D/share/gnome/bug-buddy/bug-buddy-C.omf \ 2>/dev/null || /usr/bin/true

Libtool Issues

Most, if not all, GNOME applications depend on GNU's libtool. - They also use the GNU configure system. If your port installs + They also use the GNU configure system. If your port installs shared libraries, you should add USE_LIBTOOL= yes to your port's Makefile. This takes care of most of the libtool requirements, but will not prevent things such as .la files - from being installed. To ensure a proper shared library + from being installed. To ensure a proper shared library installation, also consider adding the following line to your port's configure script directly below the line LIBTOOL_DEPS="$ac_aux_dir/ltmain.sh":

$ac_aux_dir/ltconfig $LIBTOOL_DEPS
- +
This prevents the installation of .la files and - ensures that ${PTHREAD_LIBS} will be passed to the + ensures that ${PTHREAD_LIBS} will be passed to the linker.

Distfiles

To separate GNOME 2 distfiles from the GNOME 1 distfiles, and to - keep the distfiles directory clean, GNOME 1 ports that - download their distfiles from ${MASTER_SITE_GNOME} must + keep the distfiles directory clean, GNOME 1 ports that + download their distfiles from ${MASTER_SITE_GNOME} must add the following to their Makefile:

DIST_SUBDIR= gnome
-
GNOME 2 ports that download their distfiles from +
GNOME 2 ports that download their distfiles from ${MASTER_SITE_GNOME} must include the following in their Makefile:
- +
DIST_SUBDIR= gnome2
-
Some GNOME distfiles come in both tar gzip as well as tar bzip2 +
Some GNOME distfiles come in both tar gzip as well as tar bzip2 format. To save time when downloading distfiles over slow links, you should use the bzip2 distfiles whenever possible. To do this, add the following to your port's Makefile:

USE_BZIP2= yes

If you still need help with your port, have a look at some of the existing ports for examples. The freebsd-gnome mailing list is also there for you.
&footer; diff --git a/en/gnome/docs/volunteer.sgml b/en/gnome/docs/volunteer.sgml index 30bca9f273..80e1a64caa 100644 --- a/en/gnome/docs/volunteer.sgml +++ b/en/gnome/docs/volunteer.sgml @@ -1,44 +1,44 @@ - + %gnomeincludes; %includes; ]> &header;
There is always something to do around the GNOME FreeBSD camp. Grab something that sounds interesting to you, and run with it.

-
Test existing ports, and +
Test existing ports, and report bugs.

Regularly install GNOME from packages, and report any problems with the install or the functionality.

-
Find GNOME applications not yet ported to FreeBSD, and +
Find GNOME applications not yet ported to FreeBSD, and work on porting them over.

- Subscribe to the freebsd-gnome mailing list, and help + Subscribe to the freebsd-gnome mailing list, and help answer users' questions.

-
Take patches and feedback from GNOME-related FreeBSD PRs - back to GNOME authors so that the patches can be integrated +
Take patches and feedback from GNOME-related FreeBSD PRs + back to GNOME authors so that the patches can be integrated into the next release of the application.

-
Proofread the FreeBSD GNOME project pages, +
Proofread the FreeBSD GNOME project pages, and offer feedback and updates.

Send any feedback to &email;@FreeBSD.org.
&footer; diff --git a/en/gnome/includes.xsl b/en/gnome/includes.xsl index c19b4ac12a..2686b2293b 100644 --- a/en/gnome/includes.xsl +++ b/en/gnome/includes.xsl @@ -1,35 +1,35 @@ - + FreeBSD News Home 2.4 2.5 - - - - - + + + + + @FreeBSD.org
event : diff --git a/en/gnome/news.xml b/en/gnome/news.xml index e35475a434..27dfd0bd1d 100644 --- a/en/gnome/news.xml +++ b/en/gnome/news.xml @@ -1,963 +1,963 @@ - $FreeBSD: www/en/gnome/news.xml,v 1.53 2003/12/14 16:20:40 marcus Exp $ + $FreeBSD: www/en/gnome/news.xml,v 1.54 2004/01/06 17:36:56 marcus Exp $ 2004 January 6 GNOME 2.5.2 available for FreeBSD
The GNOME 2.5.2 desktop, "You want me to blow on your toes?" release, is now available for FreeBSD. To accompany this release, the FreeBSD GNOME - team has setup an - FAQ on how to - track the GNOME development branches. Please read + team has setup an + FAQ on how to + track the GNOME development branches. Please read that to familiarize yourself with what is involved. This release can be checked out from the MarcusCom CVS repository. Also be sure to download the ``marcusmerge'' script from the same URL to merge this tree into your main ports tree.
2003 November 14 GNOME 2.5.1 available for FreeBSD -
The GNOME 2.5.1 desktop, "Hey, at least I'm +
The GNOME 2.5.1 desktop, "Hey, at least I'm housebroken" release, is now available for FreeBSD. This release is jammed packed with goodies including Evolution 1.5, gnome-network, gDesklets, and monkey-bubble. Those with iron constitutions, and a thirst for bug hunting should check out the ``ports'' module from the MarcusCom CVS repository. If you have not done so already, be sure to get the ``marcusmerge'' script from the above URL to aid in the upgrade. A man page for the script can also be found at the above URL.
November 29 GNOME 2.4.1 available for FreeBSD
The GNOME 2.4.1 desktop, the "Better late than never" release, is now available for FreeBSD. Due to the 5.2 ports freeze, GNOME 2.4.1 will not officially enter the FreeBSD ports tree until after 5.2 is released. However, it can be obtained from the MarcusCom CVS repository with the help of the ``marcusmerge'' script. For - a complete list of what's changed, checkout the + a complete list of what's changed, checkout the release announcement.
GNOME 2.5.0 available for FreeBSD
The GNOME 2.5.0 desktop, the "Obviously you're not a golfer" release, is now available for FreeBSD. FreeBSD GNOME junkies can check out this release from the MarcusCom CVS repository. Be sure to get the latest copy of the ``marcusmerge'' script while you're there to help with the upgrade. - Thanks to a few of our users, there is also a + Thanks to a few of our users, there is also a man page to go with this script. NOTE: this is a developers release, and bugs will exist. If you're not into bug-hunting, you should probably steer clear until 2.6.0 is released.
12 Pav Lucistnik joins the FreeBSD GNOME Team
Pav Lucistnik has been granted a commit bit, and has been added as the newest member of the FreeBSD GNOME team. Pav will be involved in all aspects of the FreeBSD GNOME project, and we're excited to have him aboard. Please join us all in welcoming Pav to the FreeBSD GNOME team!
- + October 24 GNOME now builds on ia64
Thanks to work by Marcel Moolenaar, the GNOME desktop now builds - on ia64. There are runtime issues to be resolved, + on ia64. There are runtime issues to be resolved, but this was expected. Most importantly, we have new - ways to exercise FreeBSD/ia64 in general and KSE/ia64 + ways to exercise FreeBSD/ia64 in general and KSE/ia64 in particular. Not to mention that we can proceed porting and building other GNOME ports. GNOME for FreeBSD now runs on i386, Alpha, Sparc64, and ia64.
16 Adam Weinberger celebrates one year with the FreeBSD GNOME Project
It's been one year since Adam Weinberger (aka adamw, aka lemniscate) signed his soul over to our project. Since then, project documentation readability is at an all-time high, we have more wacky GNOME games in the tree than ever before, and we're keeping up quicker with GNOME releases. Thanks, Adam!
September 10 GNOME 2.4.0 available for FreeBSD
The GNOME 2.4.0: "Temujin" has been released, and is now available for FreeBSD. Due to a timing conflict with the upcoming FreeBSD 4.9-RELEASE, GNOME 2.4 will not make it into the official ports tree until sometime in early October. In the meantime, you can get the ports from the MarcusCom CVS repository. Get the ``marcusmerge'' script to help you with the upgrade. If you already have this script, download it again as it has been updated. Thanks to all those who made this release possible.
4 GNOME 2.4 Release Candidate 1 available for FreeBSD
The GNOME 2.4 Release Candidate 1 (aka "Kublai") desktop - has been released and ported to FreeBSD. Those + has been released and ported to FreeBSD. Those wanting to make GNOME 2.4 the best release ever - should checkout the ``ports'' module per the + should checkout the ``ports'' module per the instructions at the MarcusCom CVS repository. Be sure to get the ``marcusmerge'' script as well to with the upgrade (even if you already have this script, download it again as it has been updated). Note, this release will identify itself as GNOME 2.3.90, but it is, in fact, GNOME 2.4 Release Candidate 1.
August 30 GNOME 2.4 Beta 2 desktop available for FreeBSD
The GNOME 2.4 Beta 2 (aka "Subotai") desktop has been released and ported to FreeBSD. This final beta is deep-frozen, meaning the final 2.4 will have very few, if any, source code changes from this release. The few, the brave, the testers should checkout the ``ports'' module per the instructions at the MarcusCom CVS repository. Be sure to get the ``marcusmerge'' script as well to help with the upgrade. Note, this release will identify itself as 2.3.7, but it is, in fact, GNOME 2.4 Beta 2.
17 GNOME 2.4 Beta 1 desktop available for FreeBSD -
The GNOME 2.4 Beta 1 (aka "Jelme") desktop has been - released, and ported to FreeBSD. For those of you - chomping at the bit to test drive this baby, checkout +
The GNOME 2.4 Beta 1 (aka "Jelme") desktop has been + released, and ported to FreeBSD. For those of you + chomping at the bit to test drive this baby, checkout the ``ports'' module per the instructions at the MarcusCom CVS repository. Be sure to get the ``marcusmerge'' script as well to help with the upgrade. Note, this release will identify itself as 2.3.6, but it is, in fact, GNOME 2.4 Beta 1. For a list of what has changed between GNOME 2.2 and 2.4 checkout http://www.ilug-cal.org/GNOME_2_4.html.
14 Alexander Nedotsukov joins the FreeBSD GNOME Team
Alexander Nedotsukov has been granted a commit bit, and has joined the FreeBSD GNOME team. - Alexander will be working on general GNOME + Alexander will be working on general GNOME desktop porting and bug-busting as well as focusing on his ports of the GNOME 2 C++ bindings. Please join us in welcoming Alexander to the team!
3 GNOME 2.3.5 desktop available for FreeBSD
The GNOME 2.3.5 desktop, the "Jebe" release, is now available for FreeBSD. Bleeding-edge GNOME fans can check out this release from the MarcusCom CVS repository. Be sure to get the ``marcusmerge'' script as well to help with the upgrade.
July 15 GNOME 1.4 Removed from FreeBSD
The GNOME 1.4 Desktop has been removed from FreeBSD. Users are encouraged to upgrade to GNOME 2.2 which offers many improvements over the older desktop. This follows the GNOME announcement that development on the 1.4 desktop had stopped.
12 GNOME 2.2.2 desktop available for FreeBSD
The GNOME 2.2.2 desktop has been released and ported to FreeBSD. GNOME 2.2.x is available in the main FreeBSD ports tree. Simply cvsup your ports, and upgrade. Packages may take a while, however. For details on what is new and what has been fixed, please see the GNOME 2.2.2 change log.
7 GNOME 2.3.3 desktop available for FreeBSD
The GNOME 2.3.3, "The Four Hounds", has been released and ported to FreeBSD. Hearty adventurers should checkout the ``ports'' module per the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi, and download the ``marcusmerge'' script to aid in the upgrade.
May 22 GNOME 2.3.2 desktop available for FreeBSD
On time, and featuring gnopernicus, the FreeBSD GNOME team presents the next GNOME 2.3 development snapshot, the "Little Hero" release. Testers should checkout the ``ports'' module per the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi, and download the ``marcusmerge'' script to aid in the upgrade.
15 GNOME 2.3.1 desktop available for FreeBSD
It's a bit late, but here none the less. For those willing to live on the edge, the next installment of the GNOME 2.3 development snapshot, code named "Daddy Walrus," has been ported. This snapshot lacks three ports found in the official GNOME distribution. They are gnopernicus, gnome-speech, and gnome-system-tools. The latter is missing because it does not fully work with FreeBSD, while the two former components rely on festival, which is broken on -CURRENT. To help out with the testing, checkout the ``ports'' module per the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi. Be sure to download the ``marcusmerge'' script as well to aid in upgrading existing ports.
April 13 GNOME 2.3.0 desktop available for FreeBSD -
Calling all testers! The first of the GNOME 2.3 +
Calling all testers! The first of the GNOME 2.3 development releases is now available. Code named "Mighty Atom," this release includes quite a few new proposed modules. The GNOME 2.3 snapshots will - become the GNOME 2.4 desktop on or around + become the GNOME 2.4 desktop on or around September 8. The full scoop can be found here. Those wanting to test this release should checkout the ``ports'' module per the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi. Be sure to download the ``marcusmerge'' script from the same page. This script will help you merge the GNOME development ports tree into your main ports tree. Send all questions to freebsd-gnome@FreeBSD.org.
4 GNOME 2.2.1 Desktop available for FreeBSD
Now that 4.8-RELEASE is out the door, the ports freeze has lifted, and GNOME 2.2.1 has been committed. GNOME 2.2.1 is a bugfix and performance release. However, it does boast "the best Nautilus ever." More details can be found at http://www.gnomedesktop.org/article.php?sid=986.
February 7 GNOME 2.2 Desktop available for FreeBSD
The GNOME 2.2 Desktop has been released, and ports are available for FreeBSD. Checkout the GNOME 2.2 release notes for the full scoop on what has changed. A list of known issues with the FreeBSD port can be found here.
January 28 GNOME 2.2 Release Candidate 2 available for FreeBSD
The GNOME 2.1.91, "OUTATIME" release, is now available, and ports have been made for FreeBSD. This is the last release candidate before GNOME 2.2 is released on February 5. For those wanting to test this - release, checkout the ``ports'' module per the + release, checkout the ``ports'' module per the instructions at - http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi. A script is + http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi. A script is also provided at that site to help in merging this tree with the official FreeBSD ports tree.
19 GNOME desktop 2.0.3 available for FreeBSD
The GNOME 2.0.3 desktop has been completed for FreeBSD after the long ports freeze to prepare for 5.0-RELEASE. This new release includes a variety of bugfixes over 2.0.2, as well as some polishing off of promised GNOME 2.0 features.
12 GNOME desktop 2.2 Release Candidate 1 available for FreeBSD -
The GNOME 2.1.90 desktop, "1.21 Jigawatts" release, is +
The GNOME 2.1.90 desktop, "1.21 Jigawatts" release, is available, and ports have been made. This is the first release candidate for GNOME 2.2, and is considered to be quite stable. People wanting to test this release should checkout the ``ports'' module per the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.
2002 December 22 GNOME 2.1.5 desktop available for FreeBSD
The GNOME 2.1.5 desktop, "Enchantment Under the Sea" release, is available and ports have been made. Testers should checkout the ``ports'' module via anonymous CVS per the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.
12 GNOME 2.1.4 desktop available for FreeBSD
The GNOME 2.1.4 desktop, "We don't need... roads" release, is available and port have been made. For those wanting to particpate in the testing, the ports are available via anonymous CVS from MarcusCom. Checkout the ``ports'' module per the - instructions at + instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.
1 - + GNOME 2.1.3 desktop available for FreeBSD
The GNOME 2.1.3 desktop, "Twin Pines" release, is available and ports have been made for it (including the GStreamer components!). For those wanting to - test this next installment in the 2.1 developer + test this next installment in the 2.1 developer series, ports are available via anonymous CVS from MarcusCom. Checkout the ``ports'' module per the - instructions at + instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.
GNOME 2 to be the default GNOME in 5.0-RELEASE
GNOME 2.0.2 will be the default GNOME desktop in the upcoming FreeBSD 5.0-RELEASE. The default desktop installation will come with both the Sawfish and Metacity window managers.
November 24 FreeBSD GNOME news updates now available in RDF format
The news updates from the FreeBSD GNOME Project can now be downloaded in RDF format. Simply point your RDF consumer at http://www.freebsd.org/gnome/news.rdf.
12 GNOME 2.1.2 desktop available for FreeBSD
The GNOME 2.1.2 desktop, "Life Preserver" release, is available, and ports have been made for most of it. There are still some FreeBSD issues with the new GStreamer stuff, and some of the newer modules (such as system-tray) haven't yet been ported. For those wanting to test this latest development snapshot, ports are available via anonymous CVS from - MarcusCom. Checkout the ``ports'' module per the - instructions at + MarcusCom. Checkout the ``ports'' module per the + instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.
October 26 GNOME 2.1.1 desktop available for FreeBSD
The GNOME 2.1.1 desktop, "Flux Capacitor" release, is available, and ports have been made for those wanting to test this next installment of the GNOME 2.2 development version. The ports are available via anonymous CVS from MarcusCom. Checkout the ``ports'' per the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.
13 GNOME 2.1.0 desktop available for FreeBSD
The GNOME 2.1.0 desktop, "88MPH" release is available, and ports have been made for those wanting to test. The ports are available - via CVS from MarcsuCom. A cvsweb interface is available from + via CVS from MarcsuCom. A cvsweb interface is available from http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi. The module name is ``ports''. Instructions for checking out the ports is available at the cvsweb site.
September 15 GNOME 2.0.2 Final Released
GNOME 2.0.2 development API and desktop has been released today (just in time for 4.7-RELEASE)! The ports tree is in sync with 2.0.2, and i386 -stable packages are available from MarcusCom.
11 GNOME 2.0.2 RC1 Released
GNOME 2.0.2 Release Candidate 1, "The Considerable Duck", is now available. The ports tree is already in sync with this release, as is the package distribution at MarcusCom.
August 15 GNOME 2.0.1 Officially Released!
GNOME 2.0.1 was officially released today. More info can be found at http://www.gnome.org/start/2.0/. The ports collection is already in sync with 2.0.1, and 2.0.1 packages are available for - i386 -stable from + i386 -stable from http://www.marcuscom.com/downloads/packages/gnome/.
14 GNOME 2 Packages Now Available! -
GNOME 2 packages for i386 FreeBSD-stable have been posted to +
GNOME 2 packages for i386 FreeBSD-stable have been posted to http://www.marcuscom.com/downloads/packages/gnome/. Both .tgz and .tbz packages have been posted. This includes everything needed to install GNOME 2 except for XFree86. These packages were built using XFree86 4.2.0 which is available in package format from a variety of locations. Please send email to freebsd-gnome@FreeBSD.org if you have any problems.
10 GNOME 2 Desktop Updated to 2.0.1 Release Candidate 1
The GNOME 2 components have now been updated to the just-announced GNOME 2.0.1 Release Candidate 1: "Not Considered Harmful" release.
June 30 GNOME 2.0 Officially Released
The FreeBSD GNOME team is proud to announce that GNOME 2.0 Release has been ported to FreeBSD. This comes four days after - the GNOME Project made their press release. Look for + the GNOME Project made their press release. Look for documentation updates to cover the new GNOME 2.0 desktop.
15 GNOME 2 components update to Release Candidate 1
GNOME 2 on FreeBSD is now up to the "Fever Pitch" RC1. This is supposedly going to be the final release candidate for GNOME 2, with a final release coming around June 21.
11 GNOME 2 components updated to the latest snapshot
GNOME 2 components have been updated to the "Release formerly known as..." release snapshot. This brings a number of GNOME 2.0 components to 2.0.0. GNOME 2.0 release is imminent!
May 28 GNOME 2 components updated to the latest snapshot
GNOME 2 components have been upgraded to "Stay on target!" release snapshot. This brings a whole new round of bug fixes and GUI improvements to GNOME 2.
21 Full port of GNOME2 beta 5 release is available
The FreeBSD GNOME Team has finished porting of GNOME2 beta 5 release to FreeBSD. All existing ports were updated and many missed were added. The FreeBSD Ports Collection now contains all bits and pieces of the GNOME2 platform, both desktop and development ones.

The team now works on improving quility of the port, by tracking down FreeBSD-specific problems and fixing them. Another goal is to provide set of pre-built GNOME2 binary packages on the official FreeBSD 4.6 release media along with GNOME 1.4 bits and pieces.
- +
We would encourage any help from our users in the form of problem reports, patches, suggestions etc.
April 26 GNOME2 ports updated to GNOME2 beta4 release
All components of GNOME2 Platform already ported to FreeBSD have been updated to the latest versions found in the official GNOME2 beta4 distribution.
6 GNOME2 ports updated to GNOME2 beta3 release
All components of GNOME2 Development Platform already ported to FreeBSD have been updated to the latest versions found in the official GNOME2 beta3 distribution.
5 Joe Clarke now committer
Joe Marcus Clarke has been granted a FreeBSD commit bit (direct access to the cvs repository). His main focus as a committer will be FreeBSD GNOME, so that expect much faster problem resolution than ever. It is also expected that he would revive somewhat stalled GNOME2 porting effort. Welcome aboard, Joe!!!
March 12 Mozilla 0.9.9 is out
Mozilla 0.9.9 is out bringing many bugfixes and new features and FreeBSD port was updated accordingly. Update is strongly recommended to all current users.
- + 11 GNOME2 ports updated to GNOME2 beta2 release
All components of GNOME2 Development Platform already ported to FreeBSD have been updated to the latest versions found in the official GNOME2 beta2 distribution. Thanks to Joe Marcus Clarke for his help.
February 10 Work on porting GNOME2 platform to FreeBSD has begun
The FreeBSD GNOME team started some initial work on getting GNOME2 bits and pieces running on FreeBSD. The work is expected to take quite some time, though some initial set of ports making up core of the GNOME2 platform would be committed to the FreeBSD ports repository as soon as possible.
January 31 New FreeBSD GNOME site up and running
Brand new FreeBSD GNOME site is up and running. Many thanks to all who make it possible, particularly Joe Marcus Clarke and John Merryweather Cooper.
29 Ade is back!
Famous Ade Lovett, who was one of the main founders of the FreeBSD GNOME porting effort, but due to various reasons had left the FreeBSD GNOME team in June 2001 decided to re-join us. This is truly amazing news, because we still have many things to do, so that his help and huge experience in the field would be really useful.
- + 28 Several core GNOME components updated
Several core GNOME ports were updated to the latest versions (gnomelibs, gnomecore, glade etc.) Please follow usual instructions to update your system.
diff --git a/en/gnome/newsflash.xsl b/en/gnome/newsflash.xsl index 20cabd5e46..43394ba098 100644 --- a/en/gnome/newsflash.xsl +++ b/en/gnome/newsflash.xsl @@ -1,105 +1,105 @@ - + - + - + - + - +

- , + , :

diff --git a/en/gnome/rss.xsl b/en/gnome/rss.xsl index 60a2b16d0b..ece173f61c 100644 --- a/en/gnome/rss.xsl +++ b/en/gnome/rss.xsl @@ -1,45 +1,45 @@ - + - + - + FreeBSD GNOME Project News http://www.FreeBSD.org/gnome FreeBSD GNOME News System <xsl:choose> <xsl:when test="count(child::title)"> <xsl:value-of select="title"/> </xsl:when> <xsl:otherwise> <xsl:value-of select="p"/> </xsl:otherwise> </xsl:choose> http://www.FreeBSD.org/gnome/newsflash# diff --git a/en/gnome/screenshots.sgml b/en/gnome/screenshots.sgml index 5458ffa0fd..5aa2d27dd2 100644 --- a/en/gnome/screenshots.sgml +++ b/en/gnome/screenshots.sgml @@ -1,46 +1,46 @@ - + %gnomeincludes; %includes; ]> &header;
Here are some examples of GNOME running on FreeBSD. Click on the thumbnails below to see a larger image.

GNOME 2.4 Screenshots

Dual screens at 2048x768 showing off the - Epiphany web browser, and the new Themus and + Epiphany web browser, and the new Themus and CD-Burner Nautilus views:

Opera, GVim with GTK+-2 support, and GDesklets all with a nice crystal icon theme:

-
Xchat, Xmms, StickyNotes, and GKrellM with the Koynacity-Blue +
Xchat, Xmms, StickyNotes, and GKrellM with the Koynacity-Blue metacity, Aquativo 1.5 GTK, and Flat blue icon themes:

GNOME 2.5 Screenshots

Galeon, RhythmBox, gpdf, Streamtuner, and Evolution 1.5, from within the very minimalistic Ion window manager. All GTK+-2 apps are using the 6nome theme:

&footer;

COMPONENT	ASSOCIATED PROGRAM	IMPLIED COMPONENTS
`atk`	`devel/atk`	`glib20`
`atspi`	`x11-toolkits/at-spi`	`gail libbonobo`
`eel2`	`x11-toolkits/eel2`	`gnomevfs2 libgnomeui gail`
`gail`	`x11-toolkits/gail`	`libgnomecanvas`
`gal2`	`x11-toolkits/gal2`	`gnomeui libgnomeprintui`
`gconf2`	`devel/gconf2`	`orbit2 libxml2 gtk20 linc`
`glib20`	`devel/glib20`	`gnometarget pkgconfig`
`gnomecontrolcenter2`	`sysutils/gnomecontrolcenter2`	`gnomedesktop metacity nautilus2`
`gnomedesktop`	`x11/gnomedesktop`	`libgnomeui`
`gnomepanel`	`x11/gnomepanel`	`libwnck gnomedesktop`
`gnomevfs2`	`devel/gnomevfs2`	`gconf2 libbonobo gnomemimedata`
`gtk20`	`x11-toolkits/gtk20`	`atk pango`
`gtksourceview`	`x11-toolkits/gtksourceview`	`libgnome libgnomeprintui`
`libartlgpl2`	`graphics/libartlgpl2`	`pkgconfig`
`libbonobo`	`devel/libbonobo`	`libxml2 orbit2`
`libbonoboui`	`x11-toolkits/libbonoboui`	`libgnomecanvas libgnome`
`libgailgnome`	`x11-toolkits/libgail-gnome`	`libgnomeui atspi`
`libgda2`	`databases/libgda2`	`glib20 libxslt`
`libglade2`	`devel/libglade2`	`libxml2 gtk20`
`libgnome`	`x11/libgnome`	`libxslt gnomevfs2 esound`
`libgnomeui`	`x11-toolkits/libgnomeui`	`libbonoboui`
`libgnomecanvas`	`graphics/libgnomecanvas`	`libglade2 libartlgpl2`
`libgnomedb`	`databases/libgnomedb`	`libgnomeui libgda2`
`libgnomeprint`	`print/libgnomeprint`	`libbonobo libartlgpl2 gtk20`
`libgnomeprintui`	`x11-toolkits/libgnomeprintui`	`libgnomeprint libgnomecanvas`
`libgsf`	`devel/libgsf`	`gnomevfs2 libbonobo`
`libgtkhtml`	`www/libgtkhtml`	`libxslt gnomevfs2 gail`
`libidl`	`devel/libIDL`	`glib20`
`libwnck`	`x11-toolkits/libwnck`	`gtk20`
`librsvg2`	`graphics/librsvg2`	`gtk20 libgsf`
`libxml2`	`textproc/libxml2`	`pkgconfig`
`libxslt`	`textproc/libxslt`	`libxml2`
`libzvt`	`x11-toolkits/libzvt`	`gtk20`
`linc`	`net/linc`	`glib20`
`nautilus2`	`x11-fm/nautilus`	`librsvg2 eel2 gnomedesktop`
`metacity`	`x11-wm/metacity`	`gconf2 glade2`
`orbit2`	`devel/ORBit2`	`libidl`
`pango`	`x11-toolkits/pango`	`glib20`
`vte`	`x11-toolkits/vte`	`gtk20`

COMPONENT	ASSOCIATED PROGRAM	IMPLIED COMPONENTS
`esound`	`audio/esound`
`gnomehack`	`gnomehack` makes common GNOME Makefile substitutions that nearly every GNOME port requires to fit into the proper mtree structure. Note: Including this option adds a `pre-patch` target to your Makefile. Therefore, only explicitly define `post-patch`.
`gnomehier`	`gnomehier` installs all the - directories needed for both the GNOME 1 and 2 desktops. + directories needed for both the GNOME 1 and 2 desktops. Only include this option if your port calls `@dirrm` on one of the directories listed in the plist for `gnomehier`.
`gnomemimedata`	`misc/gnomemimedata`	`gnomehier pkgconfig`
`gnomeprefix`	`gnomeprefix` sets some CONFIGURE_ARGS to ensure data is placed properly within the GNOME hierarchy.	`gnomehier`
`gnometarget`	`gnometarget` sets `${CONFIGURE_TARGET}` for ports whose `configure` script does not figure it out automatically.
`intlhack`	`intlhack` registers a dependency upon `textproc/intltool` and patches broken `intltool-merge.in` implementations. NOTE: Only available for the GNOME &gnomedevelver; tree.
`lthack`	`lthack` prevents the installation of .la files and ensures that `${PTHREAD_LIBS}` will be passed to the linker. NOTE: Only available for the GNOME &gnomedevelver; tree.
`pkgconfig`	`pkgconfig` registers a dependency upon `devel/pkgconfig` to make sure it is installed.

Contacts

1. What to report?

2. Where to report?

Contents

Full Text

Full Text

1. Upgrading from GNOME 2.2 to &gnomever; is tricky

2. evolution has a problem with attachments under GNOME &gnomever;

3. gstreamer doesn't play nice with rhythmbox

4. GDM crashes on startup

5. gnomemeeting fails to build

Example Makefile

GNOME Makefile Macros

GNOME 1 Desktop vs. GNOME 2 Desktop

Optional GNOME Dependencies

OMF Installation

Libtool Issues

Distfiles

GNOME 2.4 Screenshots

GNOME 2.5 Screenshots