Re: SRPM tries to build the RPM?

[Austin Gonyou <austin at coremetrics dot com>]

On Mon, 2003-08-04 at 14:23, Phil Muldoon wrote:
> Austin,
> 
> It has to install the SRPM in a temporary environment to apply patches,
> and so on so that it can give an accurate representation of the files in
> the SRPM carries. Is this what you mean?

It does all that, but it actually goes beyond that and did a full build
of all the parts of my RPM. I'm sure it's just an RPM syntax problem,
i.e. it's installing stuff in /usr/local/bin(vs
%RPM_BUILD_ROOT/usr/local/bin). Some things I inherited and haven't
fully sorted through yet. 

It would be nice if it had spec file syntax highlighting though, which
is kind of what I expected, or it just allowed one to build RPMs, after
modifying the specs, etc. I guess I was expecting it to unpack the
src.rpm and then just import all the files into the workspace, vs trying
to build anything at all. (i.e. I don't want patched versions, I want
the proper versions as they look from the SRC as I were to do rpm -ivh
some.src.rpm) so that actual modification makes more sense, regarding
the sources.

> It also invokes make on the code when you have selected the files and
> begin the import. This is is because Eclipse sees that is has a C nature
> and tries too build it. If you would like to post the logfile it
> produces (it would give you the name in the error dialog) we can take a
> look and see what is happening.

Yeah, I was wondering why RPMBUILD was being called. I was only
expecting what I noted above. 

> regards
> 
> phil

-- 
Austin Gonyou <austin@coremetrics.com>
Coremetrics, Inc.