On Mon, May 20, 2013 at 02:54:20PM +0800, Paul Wise wrote:
There are thousands of copies of config.guess/sub (or configure
scripts) out there (in tarballs) with no support for this at
all. Once it is added to config.guess/sub in git (or autoconf) then
it will take many years before the
When it comes to people building distro packages, here is another idea
thinking out loud. What's wrong with ..
$ find /tree/of/src/trees -name config.guess -exec ln -sf /etc/config.guess {}
\;
This puts the latest version into the tree, no patching required.
Ben
signature.asc
Description:
On Tue, May 21, 2013 at 2:34 AM, Ben Elliston wrote:
On Mon, May 20, 2013 at 02:54:20PM +0800, Paul Wise wrote:
There are thousands of copies of config.guess/sub (or configure
scripts) out there (in tarballs) with no support for this at
all. Once it is added to config.guess/sub in git (or
On Tue, May 21, 2013 at 7:09 AM, Ben Elliston wrote:
When it comes to people building distro packages, here is another idea
thinking out loud. What's wrong with ..
$ find /tree/of/src/trees -name config.guess -exec ln -sf /etc/config.guess
{} \;
People forgetting about the symlink during
On Tue, May 21, 2013 at 07:56:47AM -0400, Earnie Boyd wrote:
if [[ -f /usr/local/share/config/config.guess ]]
then
. /usr/local/share/config/config.guess
exit
fi
First, this does not solve the problem because it requires that every
package get a new version of config.guess. We're
On Tue, May 21, 2013 at 07:33:49AM -0400, Earnie Boyd wrote:
People forgetting about the symlink during distribution of their
package. Not all systems support it. Using cp -f would be better.
OK, fine. :-)
I think there are a few different use cases people have in mind. My
understanding of
On Tue, May 21, 2013 at 7:36 AM, Ben Elliston wrote:
Yes, but that requires re-running autoconf. I think we're trying to
avoid that because if configure.in is old, you may have a lot of work
to do to get autoreconf to work.
So in that case, a change to the start of config.guess and
On Tue, May 21, 2013 at 7:59 AM, Ben Elliston wrote:
First, this does not solve the problem because it requires that every
package get a new version of config.guess. We're trying to overcome
having to modify every package.
So that's your objection to the symlink/copy idea as well?
Second,
On Tue, May 21, 2013 at 08:21:09AM -0400, Earnie Boyd wrote:
First, this does not solve the problem because it requires that every
package get a new version of config.guess. We're trying to overcome
having to modify every package.
So that's your objection to the symlink/copy idea as
On 05/21/2013 04:59 AM, Earnie Boyd wrote:
Maybe have a common directory of /usr/[local/]share/autoconf/auxdir
and teach autoconf to look there if it doesn't find
config.guess/config.sub in the project directory and copy them when
copy is specified? I dislike the environment variable idea.
On 05/21/2013 05:56 AM, Earnie Boyd wrote:
On Tue, May 21, 2013 at 7:36 AM, Ben Elliston wrote:
Yes, but that requires re-running autoconf. I think we're trying to
avoid that because if configure.in is old, you may have a lot of work
to do to get autoreconf to work.
So in that case, a
On Tuesday 2013-05-21 07:33, Pavel Raiskup wrote:
Works for me. But we [distros] do want to mandate autoreconf anyway in the
general case: it is the *only* way to keep upstream honest about the much
hated build system not bitrotting until it decides to blow up right when we
need it for a
Works for me. But we [distros] do want to mandate autoreconf anyway in the
general case: it is the *only* way to keep upstream honest about the much
hated build system not bitrotting until it decides to blow up right when we
need it for a security update.
I know. But there is a lot of
I suggested a simple, low impact way of updating the files,
particularly for people wanting to build a large number of packages
(eg, for a distro). Can anyone tell me why this approach is not
satisfactory?
Ben
signature.asc
Description: Digital signature
On Tue, May 21, 2013 at 7:21 PM, Ben Elliston wrote:
I suggested a simple, low impact way of updating the files,
particularly for people wanting to build a large number of packages
(eg, for a distro). Can anyone tell me why this approach is not
satisfactory?
It's what I've done for years.
On Thursday 16 May 2013 15:28:39 Warren Young wrote:
On 5/15/2013 14:27, Mike Frysinger wrote:
On Wednesday 15 May 2013 15:25:31 Warren Young wrote:
we've got pretty good coverage for anything passably relevant (and then
some).
So, because Gentoo has N text editors in the repo, the N+1th
16 matches
Mail list logo
