On Thu, Mar 26, 2009 at 8:31 AM, Luca Niccoli wrote:
> After I'm done with packaging this version I'll take some time to
> understand well how the whole localization stuff is dealt with in the
> build infrastructure and I'll write upstream.
> Do you have pointers?
Nothing other than the gettext
On Thu, 26 Mar 2009 00:31:41 +0100
Luca Niccoli wrote:
> 2009/3/25 Paul Wise :
>
> > Ahhh, upstream should not be using this variable, please get them to
> > switch to the po/LINGUAS file instead. This way it should not be
> > nessecary to rebuild the configure & Makefiles in order to support an
2009/3/25 Paul Wise :
> Ahhh, upstream should not be using this variable, please get them to
> switch to the po/LINGUAS file instead. This way it should not be
> nessecary to rebuild the configure & Makefiles in order to support and
> install a new language.
After I'm done with packaging this ver
On Wed, Mar 25, 2009 at 1:56 AM, Luca Niccoli wrote:
> -ALL_LINGUAS=""
Ahhh, upstream should not be using this variable, please get them to
switch to the po/LINGUAS file instead. This way it should not be
nessecary to rebuild the configure & Makefiles in order to support and
install a new langua
2009/3/24 Daniel Leidert :
> Can you provide the patch you are applying to configure.in? It is often
Of course:
--- temp/grcm-0.1.6/configure.in2008-06-07 05:35:00.0 +0200
+++ grcm-0.1.6/configure.in 2009-03-24 00:32:09.0 +0100
@@ -22,7 +22,7 @@
AC_DEFINE_UNQUOTED(GE
Luca Niccoli wrote:
> I just refresh configure after modifying configure.in to add some
> localization support;
Can you provide the patch you are applying to configure.in? It is often
not necessary to touch this file. Sometimes you can easily patch
configure or "fix" variable values during the `m
On Tue, Mar 24, 2009 at 11:37 PM, Luca Niccoli wrote:
> Actually I'm not running automake, do I need to?
Not unless you are patching Makefile.am
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe".
2009/3/24 Paul Wise :
> In automake-based packages the recommended way to clean up after
> autotools regeneration is 'make maintainer-clean'. Unfortunately
> automake doesn't remove Makefile.in files in maintainer-clean by
> default so you may have to delete them manually or with dh_clean.
Actual
On Tue, Mar 24, 2009 at 9:42 AM, Ryan Niebur wrote:
> remove it in your clean target. since you're regenerating it, it'll be
> fine if it's not there already. and removed files don't show up in the
> .diff.gz.
>
> you should use dh_clean t(1)o remove it. (just add it to debian/clean if
> you're u
On Tue, Mar 24, 2009 at 01:37:21AM +0100, Luca Niccoli wrote:
> Hi mentors,
>
> I would like to adopt grcm.
> I'm repackaging it from scratch, since it used a rules file I was not
> confident with and didn't have a patch system.
> I need to regenerate ./configure with autoconf; I'm doing it by
> p
Hi mentors,
I would like to adopt grcm.
I'm repackaging it from scratch, since it used a rules file I was not
confident with and didn't have a patch system.
I need to regenerate ./configure with autoconf; I'm doing it by
putting autoconf in the rules file.
The problem is that this way if I build t
11 matches
Mail list logo
