Re: rpm spec file %define

2016-01-10 Thread Michael Schwendt
On Sun, 10 Jan 2016 03:16:24 +, Joseph L. Casale wrote: > I have a spec with two source files where I do not create the second, it's > not mine: > > Source0:%{name}-%{version}.tar.gz > Source1:foo-bar.tar.xz > > My prep sections looks like: > > %setup -q > %setup -q -T -D -

RE: rpm spec file %define

2016-01-10 Thread Joseph L. Casale
> That approach sounds too complicated. %setup is a macro in the %prep > section, where you can run more commands to _set up_ your builddir. The > most obvious choice IMO would be to _rename_ the versioned dir to something > unique. You could also avoid the second invocation of %setup and extract >

Re: rpm spec file %define

2016-01-11 Thread Michael Schwendt
On Sun, 10 Jan 2016 21:57:21 +, Joseph L. Casale wrote: > For the academic sake only, does a facility exist to defer evaluation > for this use case? It would get kinda ugly, but you could re-expand the macro body: %global foo-bar_dir %{expand:%(ls -d %{_builddir}/%{name}-%{version}/foo-bar-

Re: rpm spec file %define

2016-01-11 Thread Joseph L. Casale
>> For the academic sake only, does a facility exist to defer evaluation >> for this use case? > >It would get kinda ugly, but you could re-expand the macro body: > >%global foo-bar_dir %{expand:%(ls -d >%{_builddir}/%{name}-%{version}/foo-bar-*-baz |grep -o '[^/]*$')} Thanks Michael, jlc -- use