Re: gnome-common?? gnome-autogen.sh??
- From: Malcolm Tredinnick <malcolm commsecure com au>
- To: gnome-hackers <gnome-hackers gnome org>
- Subject: Re: gnome-common?? gnome-autogen.sh??
- Date: Thu, 31 Oct 2002 13:13:49 +1100
On Wed, Oct 30, 2002 at 07:25:49PM -0600, Raja R Harinath wrote:
> Havoc Pennington <hp redhat com> writes:
>
> > Naba Kumar <kh_naba gmx net> writes:
> >>
> >> Surprisingly, RedHat-8.0 doesn't ship with gnome-common. All the devel
> >> packages are installed and only gnome-common seems to be missing in the
> >> box. gnome-common contains gnome-autogen.sh and it's needed for building
> >> some (most?) gnome2 apps.
> >>
> >> I am not sure if I am missing something here. Is gnome-autogen.sh
> >> deprecated or something? Please someone let me know.
> >
> > gnome-common is a CVS-only thing. Nothing outside of cvs.gnome.org
> > should be using it, because we make no guarantees about the stability
> > of the "interface" that it presents. e.g. to move to a different
> > automake we'll just change what gnome-autogen.sh does, and that would
> > break many apps.
> >
> > Third-party apps should be using their own autogen.sh script.
>
> Is 'autogen.sh' relevant anymore? Most of the functionality is now
> in 'autoreconf' from autoconf 2.5x.
If it's only "most", then autogen.sh is still required.
The things I know of that are missing/different are that autoreconf does
not know about intltoolize and it only checks for AM_GNU_GETTEXT in
configure.in (not AM_GLIB_GNU_GETTEXT, which is the recommended one for
GNOME usage). So it basically does internationisation differently from
the way we do.
Malcolm
--
A clear conscience is usually the sign of a bad memory.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]