On 29.11.2011 23:18, Cristian Morales Vega wrote:

On 28 November 2011 18:30, Stephan Kulow wrote:

...

You may have noticed: I added libtool as buildrequire to many packages. Now that I'm through with my list, I would like to remove libtool from the projconfig. After that you need to buildrequire libtool if you need it otherwise the package will fail, but unless something slipped this should not be the case for any package in factory.

Next stop: automake

Stupid question. When I need libtool? With any package that uses autoconf/automake with libtool, only if in such a package I do an autoreconf or...

autoreconf; autogen.sh; bootstrap are the usual triggers for needing libtool. Without those calls, the libtool shipped with the .tar is used - which is fine in almost all cases. If it's not, buildrequire libtool (which requires automake, which requires autoconf). Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Wed, 21 Dec 2011, Stephan Kulow wrote:

On 28.11.2011 19:30, Stephan Kulow wrote:

...

Hi,

You may have noticed: I added libtool as buildrequire to many packages. Now that I'm through with my list, I would like to remove libtool from the projconfig. After that you need to buildrequire libtool if you need it otherwise the package will fail, but unless something slipped this should not be the case for any package in factory.

Next stop: automake

Hi,

I removed automake and autoconf from prjconf now too - and hope to have catched all cases with a submit request to fix the buildrequires.

autoconf were missed by suprisingly few packages - indeed most packages using autoconf use automake too.

In the process I made the %suse_update_config macro a wrapper for autoreconf --force --install and removed it from all packages that

Why did you do that (doing sth completely different than before) rather than define it to do nothing?! Richard. -- Richard Guenther SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer

On Thu, 22 Dec 2011, Stephan Kulow wrote:

On 22.12.2011 11:52, Richard Guenther wrote:

...

On Wed, 21 Dec 2011, Stephan Kulow wrote:

...

On 28.11.2011 19:30, Stephan Kulow wrote:

...

Hi,

You may have noticed: I added libtool as buildrequire to many packages. Now that I'm through with my list, I would like to remove libtool from the projconfig. After that you need to buildrequire libtool if you need it otherwise the package will fail, but unless something slipped this should not be the case for any package in factory.

Next stop: automake

Hi,

I removed automake and autoconf from prjconf now too - and hope to have catched all cases with a submit request to fix the buildrequires.

autoconf were missed by suprisingly few packages - indeed most packages using autoconf use automake too.

In the process I made the %suse_update_config macro a wrapper for autoreconf --force --install and removed it from all packages that

Why did you do that (doing sth completely different than before) rather than define it to do nothing?!

autoreconf does something pretty similiar - it updates the configure files, that's why. I also added a huge warning in front of it to better remove that macro - the autoreconf call after the warning is basically to show the packager if autoreconf will work.

Calling autoreconf with an autoconf version installed that does not match the one the sipped configure was created with is never a good idea. autoconf does not ensure compatibility across versions. Updating the configure files isn't pretty similar, it's simply dangerous. Richard. -- Richard Guenther SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer