public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: systemtap <systemtap@sources.redhat.com>
Subject: Re: Adding provide to systemtap.spec for systemtap-testsuite rpm
Date: Thu, 31 Jan 2008 21:43:00 -0000	[thread overview]
Message-ID: <47A240F2.2070700@redhat.com> (raw)
In-Reply-To: <47A23064.7060204@redhat.com>

Hi,

William Cohen wrote:
> Masami Hiramatsu wrote:
>> William Cohen wrote:
>>> Some people may notice that systemtap-testsuite rpm does not install without 
>>> "--nodeps" because systemtaptestsuite requires "stap", but nothing provides it. 
>>> The one line patch add a provides to the systemtap rpm and allows the 
>>> systemtap-testsuite rpm to be installed normally via rpm.
>> Instead of that, how about adding stap filtering rule to __find_requires macro?
> 
> Hi Masami,
> 
> What would be the advantage of changing the __find_requires macro? Allow 
> systemtap-test rpm to be installed by developers doing testing of locally built 
> systemtap without needing the systemtap rpm?

As far as I can see, the stap should be filtered out because it provided by
systemtap package and testsuite explicitly requires systemtap as below.

---
%package testsuite
Summary: Instrumentation System Testsuite
Group: Development/System
License: GPLv2+
URL: http://sourceware.org/systemtap/
Requires: systemtap dejagnu
---

So, anyway, developers can't install systemtap-testsuite without systemtap.

Thank you,


-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com

  reply	other threads:[~2008-01-31 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 14:27 William Cohen
2008-01-31 17:05 ` Masami Hiramatsu
2008-01-31 20:32   ` William Cohen
2008-01-31 21:43     ` Masami Hiramatsu [this message]
2008-02-01 17:03     ` Masami Hiramatsu

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=47A240F2.2070700@redhat.com \
    --to=mhiramat@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wcohen@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).