From: Tommi Virtanen <tommi.virtanen@dreamhost.com>
To: Colin McCabe <cmccabe@alumni.cmu.edu>
Cc: Brian Chrisman <brchrisman@gmail.com>,
Terrance Hutchinson <terrance.hutchinson@gmail.com>,
Jim Schutt <jaschut@sandia.gov>,
ceph-devel@vger.kernel.org
Subject: Re: RPM issues
Date: Mon, 21 Mar 2011 09:09:50 -0700 [thread overview]
Message-ID: <20110321160950.GA17804@dreamer> (raw)
In-Reply-To: <AANLkTikBxKTBz8OM+gjO5Mx0JJ3TLSxXkLYf=uioBYC1@mail.gmail.com>
On Fri, Mar 18, 2011 at 05:29:51PM -0700, Colin McCabe wrote:
> 3. How should we handle tcmalloc, if at all? Google-perftools is not
> bundled for 64 bit on CentOS. (It seems like this decision was made
> because some of the stuff in this package is buggy on 64 bit x86.
> However, tcmalloc itself is not buggy on 64 bit.). And in general, how
> do we handle things that are "good to have" but which shouldn't be
> dependencies?
Hmm. The whole point of commit a2c02d was that it'd be harder to
accidentally build a non-desired variant of Ceph. That is, just
because you reinstalled the machine you use for building the package,
and forgot to install libatomic-ops-dev, doesn't mean you should
create packages with completely different behavior in the future.
So, you need to figure out whether libatomic-ops is desired or not,
for the relevant platform/architecture. If yes, then builds must fail
without it (./configure will complain, debs have build-dependency). If
not, then say ./configure --without-libatomic-ops. But don't let it
depend on unpredictable factors.
--
:(){ :|:&};:
next prev parent reply other threads:[~2011-03-21 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 0:29 RPM issues Colin McCabe
2011-03-19 13:08 ` Ruben Kerkhof
2011-03-21 23:52 ` Colin McCabe
2011-03-21 16:09 ` Tommi Virtanen [this message]
2011-03-21 16:22 ` Colin McCabe
2011-03-21 16:31 ` Gregory Farnum
2011-03-21 16:32 ` Sage Weil
2011-03-21 17:14 ` Tommi Virtanen
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=20110321160950.GA17804@dreamer \
--to=tommi.virtanen@dreamhost.com \
--cc=brchrisman@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=cmccabe@alumni.cmu.edu \
--cc=jaschut@sandia.gov \
--cc=terrance.hutchinson@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.