From: Sage Weil <sage@newdream.net>
To: Thomas Mueller <thomas@chaschperli.ch>
Cc: ceph-devel@vger.kernel.org
Subject: Re: PATCH: ceph.spec.in
Date: Fri, 2 Jul 2010 15:22:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1007021522420.23331@cobra.newdream.net> (raw)
In-Reply-To: <i0lfkk$uhq$1@dough.gmane.org>
On Fri, 2 Jul 2010, Thomas Mueller wrote:
> Am Fri, 02 Jul 2010 21:42:38 +0200 schrieb Thomas Mueller:
>
> > On 02.07.2010 17:04, Sage Weil wrote:
> >> Applied this, sans the unpackaged files part.. those are for debugging
> >> and testing, and don't need to be installed. (That probably means
> >> 'make install' should ignore them...)
> >
> > as long as they are installed with "make install" (at least with mock)
> > the build of the packages fail with the message that there are
> > unpackaged files and no rpm's are produced.
> >
> >
> > - Thomas
>
> PS: maybe only build these binarys with debug enabled?
Done. Let me know if I missed anything?
sage
prev parent reply other threads:[~2010-07-02 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 8:13 PATCH: ceph.spec.in Thomas Mueller
2010-07-02 15:04 ` Sage Weil
2010-07-02 19:42 ` Thomas Mueller
2010-07-02 19:45 ` Thomas Mueller
2010-07-02 22:22 ` Sage Weil [this message]
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=Pine.LNX.4.64.1007021522420.23331@cobra.newdream.net \
--to=sage@newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=thomas@chaschperli.ch \
/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 NNTP newsgroup(s).