Fwd: [skalibs-2.0][PATCH] posting new clean patch (from supervision lits)

From: toki clover <tokiclover_at_gmail.com>
Date: Mon, 29 Dec 2014 10:50:23 +0100

---------- Forwarded message ----------
From: toki clover <tokiclover_at_gmail.com>
Date: 2014-12-29 10:48 GMT+01:00
Subject: Re: [skalibs-2.0][PATCH] posting new clean patch (from supervision
To: Laurent Bercot <ska-skaware_at_skarnet.org>

2014-12-29 0:31 GMT+01:00 Laurent Bercot <ska-skaware_at_skarnet.org>:

> *Contrary to what you are saying, there is no problem with libdir -
> I just tried again, to make sure. When you specify --libdir as an option,
> the value you specify overrides the default. When you do not,
> $prefix/usr/lib/<package name> is used instead, for whatever value of
> $prefix you give. And this is true for every --*dir option. There is
> no hardcoded path in the configure scripts, everything is configurable.

I am willing to respond to this...

First, anyone who has built a few packages know that when passing --libdir
to a configure script, one expect to pass the system library directory and
a package based directory. And this makes build hundreds of package easy
because no one expect to waste time again and again figuring out what to
append to `--libdir=' on a package based build. Can you image the pain to do
this on a system? Hundreds of packages does this to leverage the burden of

And when a particular package need sub-directories of the system library
directory, that package should do it in a nice way and not introduce a pain
in the arse of a well known configuration switch.

Of course, you can keep that specific libdir switch behaviour, but I've
lost some
valuable time on it... and many will certainly will bcause nobody expect to
package specific libdir on that switch.

So when I am saying the paths are a little cumbersome, to say the least, I
what I am talking about because I went to take a look and thought it would
or give an easy direction to get a _staandard build system_ which seem to be
what you're trying to do.

And yes, because you're using libdir as a package specific directory
instead of
a system directory... then there are some path hardcoded like
instead of using a standard usage like `$libdir/something'. And nobody
expect this
when one passed `--libdir=$system_libdir'! What a waste of time...
Just take a look at the configure script to see what I am talking about.

And this made me waste some valuable time and thought I'd help to avoid

It seems I am finished... I won't take the trouble to update/clean the other
patches then.

Thanks for bearing to such a long explanation.

Well, lets pass to another thing then.

Error 404: gentoo user <0123456789> was not found
Error 404: gentoo user <0123456789> was not found
Received on Mon Dec 29 2014 - 09:50:23 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:38:49 UTC