From: Eric Sandeen <sandeen@sandeen.net>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: Review: dmapi-devel RPM should required xfsprogs-devel RPM
Date: Thu, 14 Jun 2007 09:29:39 -0500 [thread overview]
Message-ID: <467150D3.7090109@sandeen.net> (raw)
In-Reply-To: <op.ttwa4bv73jf8g2@pc-bnaujok.melbourne.sgi.com>
Barry Naujok wrote:
> As per the subject (and also mentioned in the description):
>
> --- a/dmapi/build/rpm/dmapi.spec.in 2007-06-14 15:02:13.000000000 +1000
> +++ b/dmapi/build/rpm/dmapi.spec.in 2007-06-14 14:47:31.290063558 +1000
> @@ -23,7 +23,7 @@
> %package devel
> Summary: Data Management API static libraries and headers.
> Group: Development/Libraries
> -Requires: @pkg_name@ >= 2.0.4
> +Requires: @pkg_name@ >= 2.0.4 xfsprogs-devel
>
> %description devel
> dmapi-devel contains the libraries and header files needed to
>
>
seems sane to me. Just a header issue I guess?
-eric
next prev parent reply other threads:[~2007-06-14 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 5:06 Review: dmapi-devel RPM should required xfsprogs-devel RPM Barry Naujok
2007-06-14 14:29 ` Eric Sandeen [this message]
2007-06-15 0:59 ` Barry Naujok
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=467150D3.7090109@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.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