From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Status of "mplayer" in buildroot
Date: Tue, 20 Jan 2009 09:07:49 +0100 [thread overview]
Message-ID: <20090120090749.341d3958@hcegtvedt> (raw)
In-Reply-To: <200901200857.39283.markus.heidelberg@web.de>
On Tue, 20 Jan 2009 08:57:38 +0100
Markus Heidelberg <markus.heidelberg@web.de> wrote:
> Hans-Christian Egtvedt, 20.01.2009:
> > On Mon, 19 Jan 2009 20:59:47 +0100
> > Ulf Samuelsson <ulf.samuelsson@atmel.com> wrote:
> >
> > > 2) mplayer do not have any recent "versions".
> > > Instead you are encouraged to checkout the latest svn.
> > >
> >
> > It is just plain bad to depend on a random checkout. Perhaps we can
> > use debians/ubuntus "release"?
> >
> > MPlayer v1.0rc2 + mplayer_1.0~rc2-0ubuntu17.diff.gz ?
> >
> > When I look more into it, the Ubuntu diff is just adding pulse audio
> > support and various version and other doc changes.
>
> Or a Gentoo package:
> http://distfiles.gentoo.org/distfiles/mplayer-1.0_rc2_p28288.tar.bz2
>
> There we don't have to fear distribution specific stuff and exactly
> know the version we use due to the svn revision in the filename.
>
Great, that sounds a lot better.
My suggestion for my own work flow is to push the AVR32 stuff into
upstream and then grab back a subversion cut from gentoo (or other
"release") which then will incorporate the AVR32 stuff in a more sane
way.
--
Best regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2009-01-20 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 19:59 [Buildroot] Status of "mplayer" in buildroot Ulf Samuelsson
2009-01-20 6:27 ` Hans-Christian Egtvedt
2009-01-20 7:57 ` Markus Heidelberg
2009-01-20 8:07 ` Hans-Christian Egtvedt [this message]
2009-01-20 9:36 ` Peter Korsgaard
2009-01-20 9:34 ` Peter Korsgaard
2009-01-20 9:33 ` Peter Korsgaard
2009-01-20 11:00 ` Ulf Samuelsson
2009-01-20 11:29 ` Peter Korsgaard
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=20090120090749.341d3958@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