Most of your .rpmmacro file is actually redundant. Once you specify the
%_topdir rpmbuild will expect the area to be prebuilt with the SOURCES, RPMS,
etc subdirs already in place and it will look for them in the %_topdir location.
In any case, you will only need one or two entries in your .rpm
>>> On 9/24/2010 at 10:53 AM, in message <4c9cad70.3080...@gmail.com>, David
Ashley
wrote:
> I took your spec file as a starting point, but I did make a some changes I
> thought enhance and clarify things a bit more. The good news is that spec
> file
> is much cleaner, the bad news is th
I took your spec file as a starting point, but I did make a some changes I
thought enhance and clarify things a bit more. The good news is that spec file
is much cleaner, the bad news is that in some cases (Suse) you need a
.rpmmacros
files in your home directory with at least one entry (%_to
>>> On 9/23/2010 at 05:53 PM, in message <4c9bbe54.4070...@gmail.com>, David
>>> Ashley
wrote:
> All -
>
> Although not yet commited, I am playing around with the RPM spec file for
> ooRexx. I have added some new macros to the file that create additional
> information in the name of the
On Thu, Sep 23, 2010 at 1:53 PM, David Ashley
wrote:
> Although not yet commited, I am playing around with the RPM spec file for
> ooRexx. I have added some new macros to the file that create additional
> information in the name of the RPM. A typical RPM name produced by these
> macros
> looks l
All -
Although not yet commited, I am playing around with the RPM spec file for
ooRexx. I have added some new macros to the file that create additional
information in the name of the RPM. A typical RPM name produced by these macros
looks like this:
ooRexx-4.2.0-6212.fedora13.x86_64.rpm
