public inbox for eclipse@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Austin Gonyou <austin@coremetrics.com>
Cc: eclipse@sources.redhat.com
Subject: Re: SRPM tries to build the RPM?
Date: Mon, 04 Aug 2003 19:23:00 -0000	[thread overview]
Message-ID: <87n0epkzc9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1060023892.2358.39.camel@portageek.digitalroadkill.net>

>>>>> "Austin" == Austin Gonyou <austin@coremetrics.com> writes:

Austin> I tried to do an import of a SRC rpm and eclipse was actually
Austin> building the RPM. Is that proper? It failed because of the
Austin> syntax of my .spec file, but I wanted to import the src.rpm so
Austin> I could manage all my src.rpms and specs under the same IDE as
Austin> my perl, shell, and java code.

I talked to Phil about this just the other day.  And, btw, I don't
think either of us thought of this particular failure mode.

It turns out that we need to unpack the SRPM during the import
process, to give you the ability to select what files are actually
imported.

We've talked about a few different ways to change SRPM importing to
make this step unnecessary.  One idea is to just always import
everything.  Another idea is to migrate the RPM plugin toward making
it easier to do more RPM-editing steps, so for instance instead of
choosing what files to import, you would choose what patches to apply.

No real decision has been made yet.  The RPM plugin is still in its
early days.  Input is definitely welcome.

Tom

  reply	other threads:[~2003-08-04 19:23 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 [this message]
2003-08-04 19:43   ` Austin Gonyou
2003-08-04 19:23 ` Phil Muldoon
2003-08-04 19:41   ` Austin Gonyou
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=87n0epkzc9.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=austin@coremetrics.com \
    --cc=eclipse@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).