This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug releng/13768] New: systemtap.spec Requires should reflect current packaging
- From: "scox at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 27 Feb 2012 19:17:18 +0000
- Subject: [Bug releng/13768] New: systemtap.spec Requires should reflect current packaging
- Auto-submitted: auto-generated
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.