Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Lars Michelsen <lm@larsmichelsen.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] mplayer_svn: Package can be built again; Bumped to rev. 31329.
Date: Sat, 22 Jan 2011 14:31:24 +0100	[thread overview]
Message-ID: <4D3ADC2C.6070506@larsmichelsen.com> (raw)
In-Reply-To: <ihel1v$tnt$1@dough.gmane.org>

Hello,

>> A recipe can have multiple svn sources, so you can fetch ffmpeg into a
>> seperate directory then move it into the mplayer one overwriting
>> whatever mplayer checked out.
>
> Ffmpeg isn't using svn anymore, so if mplayer is using svn remote, it
> won't get updated since last week.

wow, things are changing fast. I checked out the current mplayer repo 
and it still fetches the svn repositories. But we are using old 
revisions - so this would be OK for the moment.

In a long term the mplayer_svn package could be replaced by mplayer_git 
package. mplayer_git could make use of ffmpeg git repo then, right?

So what does this mean for the mplayer_svn patch? Should I invest time 
to make it use several subversion repositories instead of the sub 
repositories?

Regards,
Lars



  reply	other threads:[~2011-01-22 13:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22  0:01 [PATCH] mplayer_svn: Package can be built again; Bumped to rev. 31329 Lars Michelsen
2011-01-22 10:59 ` Koen Kooi
2011-01-22 11:35   ` Lars Michelsen
2011-01-22 12:00     ` Graeme Gregory
2011-01-22 13:11       ` Koen Kooi
2011-01-22 13:31         ` Lars Michelsen [this message]
2011-01-22 15:17           ` Koen Kooi
2011-01-22 15:39             ` Lars Michelsen
2011-01-22 17:38             ` Lars Michelsen
2011-01-25 18:11               ` Lars Michelsen
2011-01-25 18:36                 ` Koen Kooi
2011-01-25 21:18                   ` Lars Michelsen
2011-01-25 21:45                     ` Koen Kooi
2011-01-27 17:44                       ` Lars Michelsen

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=4D3ADC2C.6070506@larsmichelsen.com \
    --to=lm@larsmichelsen.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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