From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] How handle broken or partly broken packages in the distribution
Date: Mon, 26 Jan 2009 07:05:45 +0100 [thread overview]
Message-ID: <20090126070545.1288702e@hcegtvedt> (raw)
In-Reply-To: <d6cda7730901230912g6851880fua908aad10de0192@mail.gmail.com>
On Fri, 23 Jan 2009 15:12:56 -0200
Thiago A. Corr?a <thiago.correa@gmail.com> wrote:
> On Fri, Jan 23, 2009 at 6:57 AM, Hans-Christian Egtvedt
> <hans-christian.egtvedt@atmel.com> wrote:
> >> so they are not selectable for AVR32 users
> >>
> >
> > To make it harder to fix the problem with the packages?
> >
> > It might also be a result from the development environment on your
> > build machine, like the recent alsa-utils errors somebody else
> > found on opensuse, which I have not triggered in my Ubuntu system.
> >
>
> I agree with HCE. Making packages unselectable or invisible is not a
> good approach.
> I think it would be very sufficient to just document it on the help
> string and take it out of the defconfig for that arch.
>
Or just have a Wiki with a list of all packages and which archs they
work and do not work on. Users should also see/find this table fast, so
they easily know what is expected to work and what is not.
It might even encourage users to start fiddling with packages not
working.
--
Best regards,
Hans-Christian Egtvedt
prev parent reply other threads:[~2009-01-26 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 19:07 [Buildroot] How handle broken or partly broken packages in the distribution Ulf Samuelsson
2009-01-23 8:57 ` Hans-Christian Egtvedt
2009-01-23 12:44 ` Ulf Samuelsson
2009-01-23 16:45 ` Ulf Samuelsson
2009-01-23 17:12 ` Thiago A. Corrêa
2009-01-23 17:46 ` Ulf Samuelsson
2009-01-23 21:17 ` Thiago A. Corrêa
2009-01-24 10:47 ` Ulf Samuelsson
2009-01-26 6:05 ` Hans-Christian Egtvedt [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=20090126070545.1288702e@hcegtvedt \
--to=hans-christian.egtvedt@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