All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: CityK <cityk@rogers.com>
Cc: Linux-media <linux-media@vger.kernel.org>, vincent.mcintyre@gmail.com
Subject: Re: difference mchehab/new_build.git to media_build.git ?
Date: Mon, 10 Jan 2011 10:52:41 -0200	[thread overview]
Message-ID: <4D2B0119.4030007@gmail.com> (raw)
In-Reply-To: <4D29FD05.2090501@rogers.com>

Em 09-01-2011 16:23, CityK escreveu:
> vincent.mcintyre wrote:
>> Thanks for clarifying this. Doesn't this justify a one-line NEWS item?
>> I can understand not wanting to mention it while still experimental, but now...
> 
> Last night (well, actually the wee wee hours of this morning), I took the time to:
> - add a news announcement regarding media_build on the front page of the wiki
> - update the  http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers article accordingly

Thanks for the changes!

You can add a "more advanced" approach. That's what I currently do here:

$ git clone git://linuxtv.org/media_build.git
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git media_tree
$ cd media_tree
$ git remote add linuxtv git://linuxtv.org/media_tree.git
$ git remote update
$ git checkout -b media-master remotes/linuxtv/staging/for_v2.6.38-rc1
$ cd ../media_build/linux
$ make dir DIR=../media_tree
$ cd ..

The "make dir" target will associate the development git tree with the media_tree,
in a way that, if you change a file or update the media_tree, the new_build scripts
will sync its copy with the media_tree ones, re-applying the patches if needed,
before building the targets.

You should try it. It helps a lot if you need to keep your drivers in track with the
upstream ones.

> I suspect that what has precluded any earlier case of a widely visible announcement being made, beyond those tidbits that have appeared on the mailing list, is a combination of:
> - the necessity for having someone actually find and take time to perform such an administrative task
> - and, amongst most, a case of general unfamiliarity  with the new system
> - and, a question of maintainership of the new system and whether or not its status is still classified as experimental or has reached maturity
> - and, access rights required to modify the Linuxtv proper website in regards to these developments

True. Btw, as we don't have anyone dedicated to maintain the media_build, 
I gave write rights to other people for the media_build tree. As I found
it useful to myself, I'm also keeping it on a reasonable stable (although
I only use the "make dir" way, so I probably won't notice a bug with make
untar and related targets). If someone has time and interests on helping
to maintaining it, please ping me. 

> Speaking of time, I've now expended all of mine, and then some (as per usual), which I can devote to this matter.  
> Hopefully someone can take a look and correct any mistakes I've made or add any points I've overlooked on the wiki.
> As well, hopefully someone else can take care of the other parts of the website that need to be updated.

Thanks!

Mauro.

  reply	other threads:[~2011-01-10 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 18:23 difference mchehab/new_build.git to media_build.git ? CityK
2011-01-10 12:52 ` Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-08 17:47 Martin Dauskardt
2011-01-08 17:50 ` Jarod Wilson
2011-01-09  4:01   ` Vincent McIntyre
2011-01-10 12:55     ` Mauro Carvalho Chehab

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=4D2B0119.4030007@gmail.com \
    --to=maurochehab@gmail.com \
    --cc=cityk@rogers.com \
    --cc=linux-media@vger.kernel.org \
    --cc=vincent.mcintyre@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.