Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] ed: bump to version 1.5
Date: Thu, 23 Dec 2010 13:47:48 +0100	[thread overview]
Message-ID: <20101223134748.33ba89eb@surf> (raw)
In-Reply-To: <4D133AB5.1010507@zacarias.com.ar>

On Thu, 23 Dec 2010 09:04:05 -0300
Gustavo Zacarias <gustavo@zacarias.com.ar> wrote:

> Should we go for gentargets even if they behave like auto thus making
> the package file a tad bigger/redundant?

No strong opinion on this. The thing is that as time goes, the
autotools infrastructure may make more and more assumptions on the fact
that the build system is actually autotools-based. So maybe such
packages might break in the future, so technically, GENTARGETS would be
a better fit. But as you said, this will involve quite a bit of
redundancy. Hard to say what the right (tm) solution is.

An intermediate solution is to add a comment above ED_CONF_OPT to
explain why it's done, so that if ed build breaks in the future, we're
warned that the AUTOTARGETS infrastructure has been abused by this
package.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2010-12-23 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 22:47 [Buildroot] [git commit master 1/1] ed: bump to version 1.5 Peter Korsgaard
2010-12-23  7:29 ` Thomas Petazzoni
2010-12-23  8:48   ` Peter Korsgaard
2010-12-23  8:56     ` Thomas Petazzoni
2010-12-23  9:07       ` Peter Korsgaard
2010-12-23 12:04         ` Gustavo Zacarias
2010-12-23 12:47           ` Thomas Petazzoni [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=20101223134748.33ba89eb@surf \
    --to=thomas.petazzoni@free-electrons.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