From 37cf79b70646d7a9c983bb666fc6b9b551d29b69 Mon Sep 17 00:00:00 2001 From: Maxim Sobolev Date: Tue, 22 Jan 2002 20:12:45 +0000 Subject: [PATCH] Add Maxim's blurb about using gnomedepends.py to determine what packages your port may need. --- en/gnome/docs/porting.sgml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/en/gnome/docs/porting.sgml b/en/gnome/docs/porting.sgml index fadf23cac4..af01e1c1a4 100644 --- a/en/gnome/docs/porting.sgml +++ b/en/gnome/docs/porting.sgml @@ -69,6 +69,21 @@ WANT_GNOME= yes Center, but does not use anything from GNOME Core. This option is usually used for backend APIs.

+ +

When building GNOME ports, remember that many applications + require shared directories in ${PREFIX}/share/gnome. Ports + should be constructed in a way such that files placed in these + directories are removed before the package which created the + directories (i.e. the package that has an appropriate + @dirrm in its pkg-plist). For GNOME, the principle + parent port is gnomecore. If your port incudes + USE_GNOME= yes you should be fine. If you're + uncertain if you need to require any other packages, you can use + the script ${PORTSDIR}/Tools/scripts/gnomedepends.py + to examine your port's pkg-plist.

+ +

To see a list of what packages your port will actually require, + use the command make package-depends.