[Synce-devel] new autogen.sh commit

[Mark Ellis]

Hi John

Just wondering if you really need to run ./configure at the end
of ./autogen.sh ? It creates a lot of cruft that'll get into any release
tarballs or other package building processes. Can you run it
conditionally on something in the jhbuild environment maybe ?

Just a thought.

Ta
Mark

[David Eriksson]

Post by Mark Ellis
Hi John
Just wondering if you really need to run ./configure at the end
of ./autogen.sh ? It creates a lot of cruft that'll get into any release
tarballs or other package building processes. Can you run it
conditionally on something in the jhbuild environment maybe ?

This is probably to mimic gnome-autogen.sh, but unfortunately without
support for NOCONFIGURE. This is the tail of /usr/bin/gnome-autogen.sh
from the gnome-common package in Ubuntu Dapper:

if test x$NOCONFIGURE = x; then
printbold Running $srcdir/configure $conf_flags "$@" ...
$srcdir/configure $conf_flags "$@" \
&& echo Now type \`make\' to compile $PKG_NAME || exit 1
else
echo Skipping configure process.
fi

\David

[John Carr]

Post by David Eriksson

Post by Mark Ellis
Just wondering if you really need to run ./configure at the end
of ./autogen.sh ? It creates a lot of cruft that'll get into any release
tarballs or other package building processes. Can you run it
conditionally on something in the jhbuild environment maybe ?

I presumed we were using "make dist" functionality to roll the release
tarballs, which is what jhdebuild does when its rolling debian
packages from SVN. Jonnylamb?

./autogen.sh && make distcheck

on libsynce passes and produces a libsynce tarball without the cruft.
In GNOME at least, this is generally considered the de facto test of
whether or not your autofoo is on crack.

Post by David Eriksson
This is probably to mimic gnome-autogen.sh, but unfortunately without
support for NOCONFIGURE. This is the tail of /usr/bin/gnome-autogen.sh
if test x$NOCONFIGURE = x; then
&& echo Now type \`make\' to compile $PKG_NAME || exit 1
else
echo Skipping configure process.
fi
\David

David is correct, i was trying to mimic GNOME which I assume has a
healthier implementation of autofoo than us. I considered using using
gnome-autogen.sh, but i thought it best to avoid hard GNOME build-deps
for the sanity of our KDE users.

I was initially going to svn cp, but we decided to svn mv to avoid
duplication and it would be easy to roll back if someone came up with
a severe problem.

Unless someone wants to use this opportunity to propose an alternative
build system (e.g. opensync and KDE are using cmake, which is quite
nice) then i will steal parts of gnome-autogen.sh when I get home
(tomorrow evening..) to implement NOCONFIGURE.

John

[Mark Ellis]

Post by John Carr

Post by David Eriksson

Post by Mark Ellis
Just wondering if you really need to run ./configure at the end
of ./autogen.sh ? It creates a lot of cruft that'll get into any release
tarballs or other package building processes. Can you run it
conditionally on something in the jhbuild environment maybe ?

I presumed we were using "make dist" functionality to roll the release
tarballs, which is what jhdebuild does when its rolling debian
packages from SVN. Jonnylamb?
./autogen.sh && make distcheck

That's cool, I've not often strayed into packaging territory, I'll have
to try that sometime :)

Post by John Carr
on libsynce passes and produces a libsynce tarball without the cruft.
In GNOME at least, this is generally considered the de facto test of
whether or not your autofoo is on crack.

Autofoo is always on crack, it's just more of a challenge that way.....

Post by John Carr

Post by David Eriksson
This is probably to mimic gnome-autogen.sh, but unfortunately without
support for NOCONFIGURE. This is the tail of /usr/bin/gnome-autogen.sh
if test x$NOCONFIGURE = x; then
&& echo Now type \`make\' to compile $PKG_NAME || exit 1
else
echo Skipping configure process.
fi
\David

David is correct, i was trying to mimic GNOME which I assume has a
healthier implementation of autofoo than us. I considered using using
gnome-autogen.sh, but i thought it best to avoid hard GNOME build-deps
for the sanity of our KDE users.
I was initially going to svn cp, but we decided to svn mv to avoid
duplication and it would be easy to roll back if someone came up with
a severe problem.
Unless someone wants to use this opportunity to propose an alternative
build system (e.g. opensync and KDE are using cmake, which is quite
nice) then i will steal parts of gnome-autogen.sh when I get home
(tomorrow evening..) to implement NOCONFIGURE.
John

That would be cool. It's not a big problem, just one of those things
that takes you by surprise when it happens.

Mark

[John Carr]

Post by Mark Ellis
That would be cool. It's not a big problem, just one of those things
that takes you by surprise when it happens.

Eh, my bad for not warning everyone. I was hoping to publish my
jhbuild stuff alongside it though - it's insane how quick I had a dev
environment running. And its all contained nicely in ~/sync.

Note to all: make distcheck now passes on all modules involved in
sync-engine based syncing \o/

Note to curious: make dist will give you a tarball inside the module
folder. make distcheck will give you a tarball but also ./configure &&
make && make install it to make sure its release worthy.

John