From: Vara Prasad <prasadav@us.ibm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Badari Pulavarty <pbadari@gmail.com>, systemtap@sources.redhat.com
Subject: Re: Anyone tried SystemTap with the latest RHEL5 Beta refresh
Date: Tue, 31 Oct 2006 23:15:00 -0000 [thread overview]
Message-ID: <4547D66B.3010505@us.ibm.com> (raw)
In-Reply-To: <20061030183343.GQ4978@redhat.com>
Frank Ch. Eigler wrote:
>Hi -
>
>On Mon, Oct 30, 2006 at 10:27:47AM -0800, Vara Prasad wrote:
>
>
>
>>[...] Badari is playing the role of a customer. His point of view
>>is, i have stock RHEL 5 setup, i have not made any changes to the
>>setup and trying to use systemtap and i expect it to have all the
>>pieces needed [...]
>>
>>
>
>Unfortunately, other customers prefer that systemtap's loose
>dependencies (particularly, the kernel-debuginfo) not be installed by
>default, even if they choose an "install everything" option at the
>anaconda screens. Can you think of a way of satisfying both groups?
>
>- FChE
>
>
O.k, before i think of a way to satisfy both the needs i need to
understand the objection of the other group.
The objection of other customers to not to install debuginfo package is
it because of wasted disk space due to large size of debuginfo package
or time to install or something else.
I am assuming kernel debuginfo is considered a dependency for SystemTap,
am i right.
What is the point of installing a package that doesn't work due to lack
of dependencies? In other words are we not breaking the semantics or
meaning of full package install if we don't install required
dependencies when the customer chooses a package to install.
bye,
Vara Prasad
next prev parent reply other threads:[~2006-10-31 23:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 20:43 Nguyen, Thang P
2006-10-27 0:39 ` Li Guanglei
2006-10-27 20:25 ` Badari Pulavarty
2006-10-27 21:48 ` Frank Ch. Eigler
2006-10-30 18:28 ` Vara Prasad
2006-10-30 18:33 ` Frank Ch. Eigler
2006-10-31 23:15 ` Vara Prasad [this message]
2006-11-01 1:37 ` Tim Bird
2006-11-01 2:13 ` Frank Ch. Eigler
2006-11-01 6:51 ` Gerrit Huizenga
2006-11-01 8:56 ` Ken Robson
2006-11-01 12:40 ` Frank Ch. Eigler
2006-11-01 17:20 ` David Wilder
2006-11-01 18:06 ` David Smith
2006-11-01 18:12 ` David Wilder
2006-11-01 18:23 ` Frank Ch. Eigler
2006-11-01 18:27 ` David Wilder
2006-11-01 19:31 ` Frank Ch. Eigler
2006-11-01 19:07 ` David Smith
2006-11-01 19:09 ` David Wilder
2006-11-01 19:54 ` Vara Prasad
2006-11-01 20:39 ` Michael K. Dolan Jr.
2006-11-01 20:40 ` Michael K. Dolan Jr.
2006-11-01 20:04 ` Vara Prasad
2006-11-01 21:11 ` Keshavamurthy, Anil S
2006-11-01 21:36 ` Badari Pulavarty
2006-11-01 23:47 ` William Cohen
2006-11-02 19:09 ` Badari Pulavarty
2006-11-02 19:18 ` Frank Ch. Eigler
2006-11-02 23:53 ` David Boreham
2006-11-02 23:55 ` Badari Pulavarty
2006-11-03 0:35 ` David Boreham
2006-11-03 2:22 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2006-11-01 18:51 Stone, Joshua I
2006-10-27 21:05 Nguyen, Thang P
2006-10-26 18:28 Vara Prasad
2006-10-26 20:39 ` Mike Mason
2006-10-26 22:09 ` Frank Ch. Eigler
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=4547D66B.3010505@us.ibm.com \
--to=prasadav@us.ibm.com \
--cc=fche@redhat.com \
--cc=pbadari@gmail.com \
--cc=systemtap@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).