From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnuplot : new package
Date: Fri, 4 Jan 2013 17:26:43 +0100 [thread overview]
Message-ID: <20130104172643.72321640@skate> (raw)
In-Reply-To: <50E6F604.4000401@relinux.de>
Dear Stephan Hoffmann,
On Fri, 04 Jan 2013 16:32:20 +0100, Stephan Hoffmann wrote:
> > +GNUPLOT_CONF_OPT = --without-x \
> is there a special reason for this? Why not build with x, when X11 is
> configured in buildroot?
I guess because Anthony didn't need X support. It is not because a
given software component can potentially support feature Y or Z that we
require the package submitter to support all those features Y or Z. It
would put way too much load on the initial package submitter.
Instead, we prefer having small packages that only support the features
that have been tested by the submitter, and that carefully disables all
the unsupported features. And then, as features are needed by other
people, they can submit additional patches to make those additional
features work.
Anthony: a gnuplot patch without the X support is perfectly acceptable.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-04 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 14:53 [Buildroot] [PATCH] gnuplot : new package Anthony Viallard
2013-01-04 15:15 ` Thomas Petazzoni
2013-01-04 15:38 ` Viallard Anthony
2013-01-04 15:32 ` Stephan Hoffmann
2013-01-04 16:26 ` Thomas Petazzoni [this message]
2013-01-04 17:44 ` Stephan Hoffmann
2013-01-04 18:02 ` Thomas Petazzoni
2013-01-04 18:01 ` Stephan Hoffmann
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=20130104172643.72321640@skate \
--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