From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001480]: mpfr site path changed
Date: Fri, 31 Aug 2007 17:05:19 +0200 [thread overview]
Message-ID: <46D82E2F.2050701@atmel.com> (raw)
In-Reply-To: <8e1b2f8540b63b8784b571488b1b0cd2@busybox.net>
bugs at busybox.net wrote:
<cut bug notes>
> ----------------------------------------------------------------------
> bernhardf - 08-31-07 08:07
> ----------------------------------------------------------------------
> The suggested quickfix is not the proper thing to do.
> We really want the current, stable gmp and mpfr and not an old, stale
> one.
I agree bumping the version is correct, but if the patch I sent is also
committed the user will not experience a missing mpfr when building.
Makes buildroot a bit more robust against "sudden" changes in version
numbers.
The package maintainer should bump the version number when there is a
new release IMHO.
<cut history>
--
HC
next prev parent reply other threads:[~2007-08-31 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 15:07 [Buildroot] [buildroot 0001480]: mpfr site path changed bugs at busybox.net
2007-08-31 15:05 ` Hans-Christian Egtvedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-31 14:55 bugs at busybox.net
2007-08-31 14:07 bugs at busybox.net
2007-08-31 14:03 bugs at busybox.net
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=46D82E2F.2050701@atmel.com \
--to=hcegtvedt@atmel.com \
--cc=buildroot@busybox.net \
/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