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] Help needed with cross-compiling libotr
Date: Thu, 28 Feb 2013 16:48:16 +0100	[thread overview]
Message-ID: <20130228164816.4b62ebad@skate> (raw)
In-Reply-To: <1907015096.10640.1362066181409.JavaMail.root@openwide.fr>

Dear Jeremy Rosen,

Could you please avoid top-posting, and use a decent mailer than wraps
line properly? Thanks!

On Thu, 28 Feb 2013 16:43:01 +0100 (CET), Jeremy Rosen wrote:

> I am torn on that one... the frontier between embedded and not
> embedded never was very clear, and there are lots of single-purpose
> computers that have a screen and a keyboard to run a single graphical
> app. 
> 
> I don't know the exact project here, but having a small screen
> displaying messages and implementing it with pidgin... that wouldn't
> have been my technical choice but why not...
> 
> my point is that there are lots of "obviously desktop" apps that are
> sometime used in the embedded world without pulling in the whole
> infrastructure, so in a way it makes sense to have them in buildroot.

Agreed. But what Stefan is doing is really a general-purpose
distribution, he already told about his global project on the list in
the past. So not only Pidgin is going to be packaged, but maybe also
Abiword, Firefox, and why not LibreOffice?

> the reason not to is unmaintained packages, but is it really a
> problem ? most mail we get about broken packages are fixes, not
> complaints, so I am not sure this is a problem...

To me, it is a problem. Many unmaintained packages means stuff that
will maybe no longer build, giving a bad feeling about Buildroot's
quality for newcomers. And if they still build thanks to our
autobuilders and the work we do to fix the build issues, they will
probably remain at very old versions, also giving a bad impression to
new users or potential users evaluating Buildroot.

I think we managed to keep the focus on the infrastructure (don't
generate binary packages, don't try to be too smart to guess what needs
to be rebuilt, etc.), and we also should be thinking of keeping the
focus in terms of packages.

Best 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:[~2013-02-28 15:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 15:04 [Buildroot] Help needed with cross-compiling libotr Stefan Fröberg
2013-02-28 15:06 ` Stefan Fröberg
2013-02-28 15:21 ` Thomas Petazzoni
2013-02-28 15:36   ` Markos Chandras
2013-02-28 15:43     ` Jeremy Rosen
2013-02-28 15:48       ` Thomas Petazzoni [this message]
2013-02-28 16:01         ` Stefan Fröberg
2013-02-28 15:43     ` Gustavo Zacarias
2013-02-28 15:49       ` Markos Chandras
2013-02-28 15:50         ` Thomas Petazzoni
2013-02-28 15:51           ` Gustavo Zacarias
2013-02-28 15:53           ` Markos Chandras
     [not found]   ` <512F7E8D.5070200@petroprogram.com>
2013-02-28 16:04     ` Stefan Fröberg

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=20130228164816.4b62ebad@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