Re: tracking upstream's git repo and autotools

2008-02-20 Thread Russ Allbery
martin f krafft <[EMAIL PROTECTED]> writes: > also sprach Russ Allbery <[EMAIL PROTECTED]> [2008.02.17.0033 +0100]: >> I would just Build-Depend on autoconf, automake, and the like and run >> them during the build. > > This is generally frowned upon in Debian, at least I think they > should not be

Re: tracking upstream's git repo and autotools

2008-02-20 Thread martin f krafft
also sprach Russ Allbery <[EMAIL PROTECTED]> [2008.02.17.0033 +0100]: > I would just Build-Depend on autoconf, automake, and the like and run them > during the build. This is generally frowned upon in Debian, at least I think they should not be build dependencies. See this thread: http://lists

Re: tracking upstream's git repo and autotools

2008-02-17 Thread Pierre Habouzit
On Sun, Feb 17, 2008 at 08:15:00AM +, Lars Wirzenius wrote: > On su, 2008-02-17 at 01:07 +0100, Pierre Habouzit wrote: > > Well, tell that to arm or m68k buildds. On some KDE packages, > > autoconfiguring can *literally* take hours. > > Is it just running configure that takes long, or also a

Re: tracking upstream's git repo and autotools

2008-02-17 Thread Lars Wirzenius
On su, 2008-02-17 at 01:07 +0100, Pierre Habouzit wrote: > Well, tell that to arm or m68k buildds. On some KDE packages, > autoconfiguring can *literally* take hours. Is it just running configure that takes long, or also automake and autoconf? ___ vc

Re: tracking upstream's git repo and autotools

2008-02-16 Thread Pierre Habouzit
On Sat, Feb 16, 2008 at 11:33:26PM +, Russ Allbery wrote: > Jan Luebbe <[EMAIL PROTECTED]> writes: > > > I'm trying to come up with a good way to package directly from > > upstream's git repo, which doesn't contain the files autogenerated by > > autogen.sh. > > I would just Build-Depend on au

Re: tracking upstream's git repo and autotools

2008-02-16 Thread Pierre Habouzit
On Sat, Feb 16, 2008 at 11:58:02PM +, Russ Allbery wrote: > Pierre Habouzit <[EMAIL PROTECTED]> writes: > > > It takes a lot of time, and prevents builds repeatability, in the > > sense that when autotools have backward compatibility issues, it breaks, > > not to mention that you need all th

Re: tracking upstream's git repo and autotools

2008-02-16 Thread Russ Allbery
Pierre Habouzit <[EMAIL PROTECTED]> writes: > It takes a lot of time, and prevents builds repeatability, in the > sense that when autotools have backward compatibility issues, it breaks, > not to mention that you need all the *.m4 files around to generate the > configure properly. I tend to be

Re: tracking upstream's git repo and autotools

2008-02-16 Thread Russ Allbery
Jan Luebbe <[EMAIL PROTECTED]> writes: > I'm trying to come up with a good way to package directly from > upstream's git repo, which doesn't contain the files autogenerated by > autogen.sh. I would just Build-Depend on autoconf, automake, and the like and run them during the build. -- Russ Allb