RPM Community Forums

Mailing List Message of <rpm-devel>

Re: Q: Pass --wildcards to tar on build from tarball

From: Ralf S. Engelschall <rse+rpm-devel@rpm5.org>
Date: Sat 25 Aug 2007 - 08:25:17 CEST
Message-ID: <20070825062517.GE68926@engelschall.com>
On Fri, Aug 24, 2007, Jeff Johnson wrote:

> On Aug 24, 2007, at 4:58 PM, Dmitry V. Levin wrote:
>
>> On Fri, Aug 24, 2007 at 10:45:29PM +0200, Ralf S. Engelschall wrote:
>>> On Sun, Aug 12, 2007, Dmitry V. Levin wrote:
>>>
>>>> We probably need this change, too:
>>>> http://hg.rpm.org/rpm-4.4.x?cs=1a3109298938
>>>
>>> We cannot generally assume that the tar(1) is GNU tar and providing the
>>> --wildcards option, so the patch cannot be taken over as is without
>>> breaking portability...
>>
>> You mean that we need one more configure test?
>>
>
> A configure test on the build system may be irrelevant on a "managed"
> install.
>
> I'll add a %{_tar_wildcards} wrapper, it's a silly stoopid issue.

Or even a generic %{_tar_flags} macro which can be used for passing
arbitrary flags? And perhaps the code can be adjusted to use a specific
"foo.spec" instead of "\*.spec", too? This would avoid having to
use wildcards at all...

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com
Received on Sat Aug 25 08:30:52 2007
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.