another gnome 2.22 proposal

lazyape lazyape at gmail.com
Thu Mar 27 18:53:44 CET 2008


1)
most of the gnome modules have a GNOME210_PREFIX in their BUILD script
and then a "default_make". 

We can change their BUILD scripts to something like 
"default_build" or "default_config default_make"
and add in the DETAIL or in a PRE_BUILD (?) file 
something like this:

DETAIL
    MODULE_PREFIX=$GNOMExxx_PREFIX
    #rest of DETAIL file


where xxx the version (for now 222 as 210 in the GNOME210_PREFIX).
the GNOMExxx_PREFIX is a variable that it's value is set by the lunar set command.
This because "default_config" uses the $MODULE_PREFIX variable thus the GNOMExxx_PREFIX.

example.
lunar set GNOME222_PREFIX /opt/lunar/gnome2.22
lin gnome-module  #this will build and install gnome-module in /opt/lunar/gnome2.22

lunar unset GNOME222_PREFIX
lin gnome-module #now gnome-module goes to /usr


2)
the /etc/profile.d/pkgconfig.rc file set the environmental variable PKG_CONFIG_PATH but some modules
(i.e icon-naming-utils) store their pc file in /usr/share/pkgconfig which is not in PKG_CONFIG_PATH default path. maybe something like this correct this problem

POST_INSTALL
 if [ -a $(grep -e "/usr/share/pkgconfig" /etc/profile.d/pkgconfig.rc) ]; then
   sed -i "s:\$PKG_CONFIG_PATH:/usr/share/pkgconfig\:\$PKG_CONFIG_PATH:" /etc/profile.d/pkgconfig.rc
   export PKG_CONFIG_PATH=/usr/share/pkgconfig:$PKG_CONFIG_PATH
 fi

-- 
lazyape <lazyape at gmail.com>


More information about the Lunar-dev mailing list