macros directory

[Gediminas Paulauskas <menesis delfi lt>]

I have again run into a trouble I have done myself. The way macros
subdir currently work is big pain. If a module has it's own macros in
CVS, then it's OK, until you try to use newer feature "which is handled
by some macro", like intltool. Then, someone (in the case of balsa,
gcompris, maybe others) cvs remove macros dir and add &macros to
CVSROOT/modules. And then discover, that this *doesn't work*.

$ cvs co gcompris
cvs server: existing repository /cvs/gnome/gcompris/macros does not
match /cvs/gnome/gnome-common/macros
cvs server: ignoring module macros

so you can't ./autogen.sh. I have not come to a way I could resolve the
problem, other than adding newer macros back and removing virtual
module. (I guess removing gcompris/macros physically from CVS server
would help, but no one on cvsmaster@ or #gnome could answer/help me.


Then, there is GNOME2 ports of all those apps. They do not need macros
directory. But with virtual module, you will get macros/ because there
is no way to specify a virtual module for a branch!



But there is a solution -- we do not need macros directory at all :)
If GNOME2 programs do not need it, because they have a line at the end
of ./autogen.sh:

USE_GNOME2_MACROS=1 . gnome-autogen.sh

it is even simplier for GNOME 1 apps -- you even don't need to define a
variable :)

. gnome-autogen.sh

Of course, there is more nice things to check if gnome-autogen.sh exist,
find it if it's in share directory, print error that you need to install
gnome-common -- just look into autogen.sh scripts of nautilus or
libgnome.

Then you can remove macros subdir, &macros module, ditch it from
Makefiles and configures...


I just need to ask -- is this correct?

-- 
Gediminas