Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of VLC build failures
Date: Tue, 25 Feb 2014 21:25:29 +0100	[thread overview]
Message-ID: <87ppmbhrd2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <530CCB9B.2000101@mind.be> (Arnout Vandecappelle's message of "Tue, 25 Feb 2014 17:58:03 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 >> When I (re-)added this package, I had hoped to have more time to spend
 >> on getting it working properly. (As it happens, the project for which
 >> I needed vlc has now been abandoned.)
 >> 
 >> I tend to agree that this is a potentially "high profile" package, and
 >> that it ought perhaps to be dropped from the 2014.02 release.

 >  I would also be OK with adding a comment to the VLC config option that
 > warns the users that it is not working very well.

 >  I can send a patch if needed.

Yes, please.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-25 20:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-22 Thomas Petazzoni
2014-02-23 10:00 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2014-02-23 10:16   ` Thomas De Schampheleire
2014-02-23 10:56     ` Thomas Petazzoni
2014-02-23 15:45   ` Peter Korsgaard
2014-02-23 23:46   ` Ezequiel García
2014-02-24 21:16     ` Thomas Petazzoni
2014-02-24 21:18       ` Ezequiel García
2014-02-26 21:10         ` Thomas Petazzoni
2014-02-24 10:12   ` Vicente Olivert Riera
2014-02-24 10:30     ` Vicente Olivert Riera
2014-02-25  7:15   ` [Buildroot] Analysis of VLC " Arnout Vandecappelle
2014-02-25 15:17     ` Simon Dawson
2014-02-25 16:58       ` Arnout Vandecappelle
2014-02-25 20:25         ` Peter Korsgaard [this message]
2014-02-25 18:14     ` Thomas Petazzoni
2014-02-25 21:08   ` [Buildroot] Analysis of " Samuel Martin

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=87ppmbhrd2.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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