public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug releng/13768] New: systemtap.spec Requires should reflect current packaging
Date: Mon, 27 Feb 2012 19:18:00 -0000	[thread overview]
Message-ID: <bug-13768-6586@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13768

             Bug #: 13768
           Summary: systemtap.spec Requires should reflect current
                    packaging
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: releng
        AssignedTo: systemtap@sourceware.org
        ReportedBy: scox@redhat.com
    Classification: Unclassified


The Requires and Buildrequires need to reflect the current packaging scheme.

<jistone> for one, gcc and make are part of the core build environment, so
don't
  need buildrequires (per packaging guidelines) and systemtap-devel does need
  the real Requires to do anything useful
<fche> but not gcc-c++; that should go into buildrequires
<jistone> I doubt gcc-c++ too, checking...
  http://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions_2
<fche> hm, interesting; I had run yum-builddep systemtap before and ended up
  without gcc-c++ in the system 'no need' at least does not mean 'forbidden'
<jistone> yum-builddep doesn't account for that list I'm not sure actually if
  there's an easy way to install that list... some group perhaps
<fche> IMO let's leave at least gcc-c++ in the buildreq's (that's the only one
  I'd had problems with)
<fche> not requires: gcc-c++; we don't build c++ modules just gcc, make
<jistone> the testsuite probably wants gcc-c++ though
<fche> (and glibc-devel.i386 + glibc-devel.x86-64 ... if that were easily
  expressed)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-02-27 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 19:18 scox at redhat dot com [this message]
2012-03-02 16:13 ` [Bug releng/13768] " fche at redhat dot com

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=bug-13768-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /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).