difference mchehab/new_build.git to media_build.git ?

difference mchehab/new_build.git to media_build.git ?

[Martin Dauskardt]

Since some months I didn't test any new drivers, because I don't  want to run 
an unstable kernel. The v4l-dvb hg is obviously dead, although I never read a 
formally announcement. Requests remain unanswered 
(http://article.gmane.org/gmane.linux.drivers.video-input-
infrastructure/27069/)

In the german vdrportal forum we recently "discovered"  
git://linuxtv.org/mchehab/new_build.git as a possibility to build and test 
current drivers with the kernels in current Distributions.

Now I see a discussion about media_built, which seems to be 
git://linuxtv.org/media_build.git. 

What is the difference between media_build and new_build?

I am getting more and more confused...

Re: difference mchehab/new_build.git to media_build.git ?

[Jarod Wilson]

On Jan 8, 2011, at 12:47 PM, Martin Dauskardt wrote:

> Since some months I didn't test any new drivers, because I don't  want to run 
> an unstable kernel. The v4l-dvb hg is obviously dead, although I never read a 
> formally announcement. Requests remain unanswered 
> (http://article.gmane.org/gmane.linux.drivers.video-input-
> infrastructure/27069/)
> 
> In the german vdrportal forum we recently "discovered"  
> git://linuxtv.org/mchehab/new_build.git as a possibility to build and test 
> current drivers with the kernels in current Distributions.
> 
> Now I see a discussion about media_built, which seems to be 
> git://linuxtv.org/media_build.git. 
> 
> What is the difference between media_build and new_build?

There's no difference. It started out at mchehab/new_build.git, then got moved
to media_build.git, but there's a symlink in place to keep from breaking things
for people who originally checked it out at the old location.

The move essentially promoted it from "something Mauro's tinkering with" to
"something generally useful for a wider audience". And its also being worked on
by more people than just Mauro now (myself included).

-- 
Jarod Wilson
jarod@wilsonet.com

Re: difference mchehab/new_build.git to media_build.git ?

[Vincent McIntyre]

> There's no difference. It started out at mchehab/new_build.git, then got
> moved
> to media_build.git, but there's a symlink in place to keep from breaking
> things
> for people who originally checked it out at the old location.
>
> The move essentially promoted it from "something Mauro's tinkering with" to
> "something generally useful for a wider audience". And its also being worked
> on
> by more people than just Mauro now (myself included).

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...

Vince

Re: difference mchehab/new_build.git to media_build.git ?

[Mauro Carvalho Chehab]

Em 09-01-2011 02:01, Vincent McIntyre escreveu:
>> There's no difference. It started out at mchehab/new_build.git, then got
>> moved
>> to media_build.git, but there's a symlink in place to keep from breaking
>> things
>> for people who originally checked it out at the old location.
>>
>> The move essentially promoted it from "something Mauro's tinkering with" to
>> "something generally useful for a wider audience". And its also being worked
>> on
>> by more people than just Mauro now (myself included).
> 
> 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...

I was actually waiting for someone to manifest as being the maintainer of it,
before doing that announcement, but it is probably fine to add it.

I can add it later, but I'm a little busy this week. So, if someone could prepare
me the news text (in HTML, if possible), this would help a lot.

Cheers,
Mauro

Re: difference mchehab/new_build.git to media_build.git ?

[CityK]

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

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

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.

Re: difference mchehab/new_build.git to media_build.git ?

[Mauro Carvalho Chehab]

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.