public inbox for
 help / color / mirror / Atom feed
From: Austin Gonyou <>
Subject: Re: SRPM tries to build the RPM?
Date: Mon, 04 Aug 2003 19:41:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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 <>
Coremetrics, Inc.

  reply	other threads:[~2003-08-04 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 19:17 Austin Gonyou
2003-08-04 19:23 ` Tom Tromey
2003-08-04 19:43   ` Austin Gonyou
2003-08-04 19:23 ` Phil Muldoon
2003-08-04 19:41   ` Austin Gonyou [this message]
2003-08-04 20:06     ` Phil Muldoon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).