Re: Integrate ITS Tool with gettext and Autotools (Was: Re: Death of gnome-common)

On Fri, Oct 02, 2015 at 04:48:31PM -0400, Shaun McCance wrote: > On Fri, 2015-10-02 at 19:55 +0200, Sébastien Wilmet wrote: > > So a solution is to add the generated *.pot files to Git. > > > > Is there another solution? > > This is what yelp and yelp-xsl do. They have XML files of translated >

Re: Integrate ITS Tool with gettext and Autotools (Was: Re: Death of gnome-common)

On Sat, Oct 3, 2015 at 12:49 AM, Alexandre Franke < alexandre.fra...@gmail.com> wrote: > On Sat, Oct 3, 2015 at 4:40 AM, Philip Chimento > wrote: > > For what it's worth, I break that rule for .pot files in my own projects, > > because adding them to Git makes it

Re: Integrate ITS Tool with gettext and Autotools (Was: Re: Death of gnome-common)

On Sat, Oct 3, 2015 at 4:40 AM, Philip Chimento wrote: > For what it's worth, I break that rule for .pot files in my own projects, > because adding them to Git makes it easier for people who aren't comfortable > with the command line to contribute translations. Are you

Integrate ITS Tool with gettext and Autotools (Was: Re: Death of gnome-common)

Hi, On Wed, Jun 24, 2015 at 02:17:52PM +0100, Emmanuele Bassi wrote: > On 24 June 2015 at 14:13, Michael Catanzaro wrote: > > On Wed, 2015-06-24 at 08:56 +0100, Emmanuele Bassi wrote: > >> I do hope that, if you're using glib-gettext or intltool, you spend a > >> little bit

Re: Integrate ITS Tool with gettext and Autotools (Was: Re: Death of gnome-common)

On Fri, 2015-10-02 at 19:55 +0200, Sébastien Wilmet wrote: > Hi, > > On Wed, Jun 24, 2015 at 02:17:52PM +0100, Emmanuele Bassi wrote: > > On 24 June 2015 at 14:13, Michael Catanzaro > > wrote: > > > On Wed, 2015-06-24 at 08:56 +0100, Emmanuele Bassi wrote: > > > > I do hope

Re: Integrate ITS Tool with gettext and Autotools (Was: Re: Death of gnome-common)

On Fri, Oct 2, 2015 at 10:55 AM, Sébastien Wilmet wrote: > I've tried to not add the generated *.pot files to Git, because > generated files should not be added to the version control system. For what it's worth, I break that rule for .pot files in my own projects, because

Re: Death of gnome-common

On 16 August 2015 at 10:31, Sébastien Wilmet swil...@gnome.org wrote: Hi, Hi Sébastien, On Thu, May 28, 2015 at 12:47:47PM +0100, Philip Withnall wrote: There’s a migration guide here: https://wiki.gnome.org/Projects/GnomeCommon/Migration We’ve tried to make the transition as easy and

Re: Death of gnome-common

On Fri, Aug 21, 2015 at 04:18:09PM -0500, Michael Catanzaro wrote: On Sun, 2015-08-16 at 11:31 +0200, Sébastien Wilmet wrote: --install has been added to the ACLOCAL_AMFLAGS. You don't want to touch that (in Makefile.am) anymore; see:

Re: Death of gnome-common

On Tue, Aug 18, 2015 at 08:36:43AM +0100, Philip Withnall wrote: Do you know what's wrong? Do we need to do something about it? Just ignore the message. Added to the wiki, in the FAQ. -- Sébastien ___ desktop-devel-list mailing list

Re: Death of gnome-common

On Sat, 2015-08-22 at 10:45 +0200, Sébastien Wilmet wrote: On Fri, Aug 21, 2015 at 04:18:09PM -0500, Michael Catanzaro wrote: On Sun, 2015-08-16 at 11:31 +0200, Sébastien Wilmet wrote: --install has been added to the ACLOCAL_AMFLAGS. You don't want to touch that (in Makefile.am)

Re: Death of gnome-common

On Sat, 2015-08-22 at 12:11 +0200, Sébastien Wilmet wrote: On Tue, Aug 18, 2015 at 08:36:43AM +0100, Philip Withnall wrote: Do you know what's wrong? Do we need to do something about it? Just ignore the message. Added to the wiki, in the FAQ. The messages are coming from

Re: Death of gnome-common

On Sun, 2015-08-16 at 11:31 +0200, Sébastien Wilmet wrote: --install has been added to the ACLOCAL_AMFLAGS. You don't want to touch that (in Makefile.am) anymore; see: https://mail.gnome.org/archives/desktop-devel-list/2015-June/msg9.h tml

Re: Death of gnome-common

Hey, On Sun, 2015-08-16 at 11:31 +0200, Sébastien Wilmet wrote: On Thu, May 28, 2015 at 12:47:47PM +0100, Philip Withnall wrote: There’s a migration guide here: https://wiki.gnome.org/Projects/GnomeCommon/Migration We’ve tried to make the transition as easy and smooth as possible,

Re: Death of gnome-common

Sébastien Wilmet swil...@gnome.org writes: I've migrated GtkSourceView, and now when running autogen.sh I see those messages: + glib-gettextize --force --copy Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4

Re: Death of gnome-common

On Mon, Aug 17, 2015 at 08:06:15PM +0900, Daiki Ueno wrote: Sébastien Wilmet swil...@gnome.org writes: I've migrated GtkSourceView, and now when running autogen.sh I see those messages: + glib-gettextize --force --copy Copying file po/Makefile.in.in Please add

Re: Death of gnome-common

Hi, On Thu, May 28, 2015 at 12:47:47PM +0100, Philip Withnall wrote: There’s a migration guide here: https://wiki.gnome.org/Projects/GnomeCommon/Migration We’ve tried to make the transition as easy and smooth as possible, but there will inevitably be hiccups. Please let me know about

Re: Death of gnome-common

On Sat, 2015-05-30 at 08:09 -0500, Michael Catanzaro wrote: This is a nit, but I think the 'set -x' to 'set +x' at the end of the sample autogen.sh is too expansive, since it results in the conditional tests being printed as independent statements: Another problem is that the 'set +x' gets

Re: Death of gnome-common

On Tue, 2015-06-23 at 22:24 -0500, Michael Catanzaro wrote: On Tue, 2015-06-23 at 08:33 +0100, Philip Withnall wrote: As Kalev says, we should ensure this still builds with various distros. RHEL7 is fine. Debian stable (Jessie) has 1.14. Fedora has had ≥ 1.13 for a long time. Arch has

Re: Death of gnome-common

Hi; On 23 June 2015 at 23:41, Philip Withnall phi...@tecnocode.co.uk wrote: Hey Emmanuele, Philip On Tue, 2015-06-23 at 17:08 +0100, Emmanuele Bassi wrote: that's usually better replaced by: autoreconf -if || exit $? test -n $NOCONFIGURE ./configure $@ Which isn't shorter, but it's

Re: Death of gnome-common

On Wed, 2015-06-24 at 22:38 +0200, Michael Biebl wrote: 2015-06-24 9:56 GMT+02:00 Emmanuele Bassi eba...@gmail.com: On 23 June 2015 at 23:41, Philip Withnall phi...@tecnocode.co.uk wrote: What if your module uses glib-gettext, gtk-doc, or intltool? I do hope that, if you're using

Re: Death of gnome-common

Hi, 2015-06-24 9:56 GMT+02:00 Emmanuele Bassi eba...@gmail.com: On 23 June 2015 at 23:41, Philip Withnall phi...@tecnocode.co.uk wrote: What if your module uses glib-gettext, gtk-doc, or intltool? I do hope that, if you're using glib-gettext or intltool, you spend a little bit of time to

Re: Death of gnome-common

On Wed, 2015-06-24 at 08:56 +0100, Emmanuele Bassi wrote: I do hope that, if you're using glib-gettext or intltool, you spend a little bit of time to port to upstream gettext instead. Has anyone written a guide on how to do this? I thought intltool was preferred. We definitely need better

Re: Death of gnome-common

On Wed, 2015-06-24 at 09:21 +0100, Philip Withnall wrote: libtoolize complains about it: libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. But I guess libtoolize is wrong. Is there an upstream bug report? No need. I have libtool 2.4.2 provided by Fedora 22,

Re: Death of gnome-common

On Wed, 2015-06-24 at 08:57 -0500, Michael Catanzaro wrote: On Wed, 2015-06-24 at 14:17 +0100, Emmanuele Bassi wrote: Sadly, it's still in use for AppData XML, but for that (and any other XML-based format) there's itstool, which is also used by the documentation team for the application

Re: Death of gnome-common

Hi; On 24 June 2015 at 14:13, Michael Catanzaro mcatanz...@gnome.org wrote: On Wed, 2015-06-24 at 08:56 +0100, Emmanuele Bassi wrote: I do hope that, if you're using glib-gettext or intltool, you spend a little bit of time to port to upstream gettext instead. Has anyone written a guide on

Re: Death of gnome-common

On Wed, 2015-06-24 at 14:17 +0100, Emmanuele Bassi wrote: Sadly, it's still in use for AppData XML, but for that (and any other XML-based format) there's itstool, which is also used by the documentation team for the application help: http://itstool.org/ I will wait for someone to replace

Re: Death of gnome-common

On Wed, 2015-06-24 at 08:31 -0500, Michael Catanzaro wrote: On Wed, 2015-06-24 at 09:21 +0100, Philip Withnall wrote: libtoolize complains about it: libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. But I guess libtoolize is wrong. Is there an

Re: Death of gnome-common

On Mon, Jun 22, 2015 at 12:01 AM, Philip Withnall phi...@tecnocode.co.uk wrote: On Sun, 2015-06-21 at 17:56 -0700, Jasper St. Pierre wrote: On Thu, May 28, 2015 at 9:05 AM, Philip Withnall phi...@tecnocode.co.uk wrote: See literally the first migration item on

Re: Death of gnome-common

Hi Philip; that's usually better replaced by: autoreconf -if || exit $? test -n $NOCONFIGURE ./configure $@ Which isn't shorter, but it's pretty much to the point and works fine in jhbuild and autobuilders. Ciao, Emmanuele. On 23 June 2015 at 16:54, Philip Chimento

Re: Death of gnome-common

On Tue, 2015-06-23 at 08:33 +0100, Philip Withnall wrote: As Kalev says, we should ensure this still builds with various distros. RHEL7 is fine. Debian stable (Jessie) has 1.14. Fedora has had ≥ 1.13 for a long time. Arch has 1.15. FreeBSD has 1.15. So unless anybody objects, I think a

Re: Death of gnome-common

On Mon, 2015-06-22 at 10:44 -0500, Michael Catanzaro wrote: On Mon, 2015-06-22 at 16:36 +0100, Philip Withnall wrote: Do we require automake 1.13 though? Looks like it was released January 1, 2013... so we should. We *could*; doesn’t necessarily mean we *should*. Automake 2.0 isn’t out

Re: Death of gnome-common

Hey Emmanuele, Philip On Tue, 2015-06-23 at 17:08 +0100, Emmanuele Bassi wrote: that's usually better replaced by: autoreconf -if || exit $? test -n $NOCONFIGURE ./configure $@ Which isn't shorter, but it's pretty much to the point and works fine in jhbuild and autobuilders. What if

Re: Death of gnome-common

On Sun, 2015-06-21 at 19:54 -0500, Michael Catanzaro wrote: OK, next problem. The porting guide says: Firstly, add AC_CONFIG_MACRO_DIR([m4]) to your configure.ac, and ACLOCAL_AMFLAGS = --install -I m4 ${ACLOCAL_FLAGS} to your top-level Makefile.am, regardless of which of the two

Re: Death of gnome-common

On 06/22/2015 05:44 PM, Michael Catanzaro wrote: On Mon, 2015-06-22 at 16:36 +0100, Philip Withnall wrote: Do we require automake 1.13 though? Looks like it was released January 1, 2013... so we should. Automake 2.0 isn’t out yet (though it looks cool), so I’d be tempted to leave in the

Re: Death of gnome-common

On Mon, 2015-06-22 at 16:36 +0100, Philip Withnall wrote: Do we require automake 1.13 though? Looks like it was released January 1, 2013... so we should. Automake 2.0 isn’t out yet (though it looks cool), so I’d be tempted to leave in the ACLOCAL_AMFLAGS recommendation for backwards

Re: Death of gnome-common

On Sun, 2015-06-21 at 17:56 -0700, Jasper St. Pierre wrote: On Thu, May 28, 2015 at 9:05 AM, Philip Withnall phi...@tecnocode.co.uk wrote: See literally the first migration item on https://wiki.gnome.org/Projects/GnomeCommon/Migration tl;dr: You can open-code it with essentially:

Re: Death of gnome-common

On Thu, May 28, 2015 at 9:05 AM, Philip Withnall phi...@tecnocode.co.uk wrote: See literally the first migration item on https://wiki.gnome.org/Projects/GnomeCommon/Migration tl;dr: You can open-code it with essentially: aclocal --install || exit 1 glib-gettextize --force

Re: Death of gnome-common

On Sat, 2015-05-30 at 08:09 -0500, Michael Catanzaro wrote: This is a nit, but I think the 'set -x' to 'set +x' at the end of the sample autogen.sh is too expansive, since it results in the conditional tests being printed as independent statements: Good nit. Please feel free to update the wiki

Re: Death of gnome-common

This is a nit, but I think the 'set -x' to 'set +x' at the end of the sample autogen.sh is too expansive, since it results in the conditional tests being printed as independent statements: autoreconf: Leaving directory `.' + '[' '' = '' ']' + ./configure --prefix /home/mcatanzaro/jhbuild/install

Death of gnome-common

Hi all, This cycle, Dave and I are planning for the last ever release of gnome-common. A lot of its macros for deprecated technologies (scrollkeeper?!) have been removed, and the remainder of its macros have found better replacements in autoconf-archive[1], where they can be used by everyone, not

Re: Death of gnome-common

Would this make sense to create a GNOME Goal[1] to ease/track the change? [1] https://wiki.gnome.org/action/show/Initiatives/GnomeGoals?action=showredirect=GnomeGoals 2015-05-28 13:47 GMT+02:00 Philip Withnall phi...@tecnocode.co.uk: Hi all, This cycle, Dave and I are planning for the last

Re: Death of gnome-common

It’s already sort of tracked as part of the ModernAutotools goal, although that one lost momentum a while ago, so its status needs to be reset: https://wiki.gnome.org/Initiatives/GnomeGoals/ModernAutotools However, since there’s no flag-day-changeover for gnome-common, I’m not sure it’s

Re: Death of gnome-common

See literally the first migration item on https://wiki.gnome.org/Projects/GnomeCommon/Migration tl;dr: You can open-code it with essentially: aclocal --install || exit 1 glib-gettextize --force --copy || exit 1 gtkdocize --copy || exit 1 intltoolize --force --copy

Re: Death of gnome-common

What about the gnome-autogen.sh script? Most of my autogen.sh files just run . gnome-autogen.sh On Thu, May 28, 2015 at 6:55 AM, Daniel Mustieles García daniel.mustie...@gmail.com wrote: Ok, thanks for clarifying! :) 2015-05-28 14:40 GMT+02:00 Philip Withnall phi...@tecnocode.co.uk: It’s