discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] [UHD 3.8.0] Release Announcement


From: Martin Braun
Subject: Re: [Discuss-gnuradio] [UHD 3.8.0] Release Announcement
Date: Wed, 29 Oct 2014 18:10:46 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

On 10/29/2014 03:35 PM, Rick Farina wrote:
>> - We have reorganized the firmware and fpga subdirectories. The former
>> was simply moved around, but the latter is now a git submodule. Run 'git
>> submodule init' and 'git submodule update' if you want to read and
>> change the fppga source code. As a result, the source tarballs will be
>> much smaller.
> 
> I'm trying to update gentoo but I don't actually see an update for the
> firmware images here:
> 
> http://files.ettus.com/binaries/master_images/
> 
> I only see rc1.  Also of note, typically releases are always put into
> archive/ at the same time so we have a link that will be valid for the
> longer term.

Thanks for pointing this out -- this was another change. First, for
anyone using uhd_images_downloader, nothing changes. That'll still work.
Also, I have added the files to the usual location, so the manual
download folks will not have to sift through a long list of images.
In fact, for 99% of the UHD users population, nothing changes.

So, what *did* change? Mainly, our main place for images is >
http://files.ettus.com/binaries/images/ from now on; files will not get
moved to an archive later on.

A quick motivation (and remember this is for a few people out there who
want to package stuff etc.): We want to be able to deploy a valid image
set for any given commit, and any branch -- not just maint and master.
This is of course for our dev process, but we also may be releasing
other branches to the public in the future.
In the directory images/ in the repo, you'll find a set of tools to grab
the correct image set for any given commit (starting with 3.8). Running
populate_imgs.py will dump a valid set of images into your soure tree.
We internally use this to generate the publically available .debs and .rpms.

I hope this answers this question!

Cheers,
Martin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]