Re: [Discuss-gnuradio] PyBombs install maint branch from fresh

[Marcus Müller]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Agreed, that's why I like the idea of GR being maint by default (so
that dependencies might not change that easily [hoping that maint is
always tested with the minimum required versions]) and letting users
who might want to risk the breakage just choose their version to their
liking -- obviously, if you take a different version than the recipe
maintainer thought would be right for you, you're leaving the safe
path, and no one can really help you there if you have funky version
problems.

Greetings,
Marcus

On 23.07.2014 14:36, Tim wrote:
> One of the problems with allowing this kind of customization is
> that a single set of pybombs recipes is generally intended to
> represent a fixed set of versions / branches as far as
> configuration management. Supporting additional branch combinations
> is kind of explosive in terms of new combinations of supported
> packages/versions.    That said, master is kind of a moving target.
> The hope was to have a set of recipes that tracks master everywhere
> for the most part (for developers that want this), and then have
> numbered known good sets of recipes that track for instance 3.7.3
> or 3.7.4 with known good OOT modules at the time (for more stable
> OOT development or pure users).   However this is a lot of 
> time/work to set up and constantly test / release so thus far we
> haven't really been doing that half - The versioned releases are to
> some extent already covered by binary packages - That said, we can
> always throw this feature in with a *danger untested version
> combination* caveat ...
> 
> -Tim
> 
> 
> On 07/23/2014 07:28 AM, Marcus Müller wrote: Tim,
> 
> idea: pybombs install package gets the default branch as in the
> recipe, pybombs install package%awesomefeatures gets the
> awesomefeatures branch.
> 
> That would allow people to specify they want UHD maint, GNU Radio 
> v3.7.4, and gqrx master, if they really want to.
> 
> Greetings, Marcus
> 
> On 23.07.2014 13:18, Tim O'Shea wrote:
>>>> Martin, You are probably right we should track maint by
>>>> default at this point.    I think it's worth adding a Pybombs
>>>> environment question about which branch to track during
>>>> initial setup for those that prefer to track master however.
>>>> Tim On Jul 23, 2014 7:10 AM, "Activecat"
>>>> <address@hidden> wrote:
>>>> 
>>>>> On Wed, Jul 23, 2014 at 5:16 PM, Martin Braun 
>>>>> <address@hidden> wrote:
>>>>> 
>>>>>> On 07/23/2014 07:14 AM, Activecat wrote:
>>>>>>> Dear Sirs,
>>>>>>> 
>>>>>>> I am performing fresh gnuradio installation using
>>>>>>> pybombs. Pybombs install master branch by default. How
>>>>>>> to make pybombs install 'maint' instead?
>>>>>>> 
>>>>>>> address@hidden: ~/download/pybombs $ git checkout maint
>>>>>>> error: pathspec 'maint' did not match any file(s) known
>>>>>>> to git.
>>>>>> This is not how you use git; you need to give it a
>>>>>> remote branch to track first. Also, if you checked out
>>>>>> 'maint' on pybombs, it wouldn't necessarily check out
>>>>>> 'maint' on any SW package it's trying to install.
>>>>>> 
>>>>>> I assume you're trying to install GNU Radio maint, right?
>>>>>> I guess one way would be to modify the gnuradio.lwr
>>>>>> recipe, change the default branch to maint.
>>>>>> 
>>>>>> M
>>>>>> 
>>>>>> 
>>>>> Thanks. yes, I am trying to install GNU Radio maintenance 
>>>>> branch. I will change the gitbranch of gnuradio.lwr recipe
>>>>> to 'maint'. Does this means the uhd.lwr also need to be
>>>>> 'maint', or can just be 'master' as default?
>>>>> 
>>>>> _______________________________________________
>>>>> Discuss-gnuradio mailing list address@hidden 
>>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Discuss-gnuradio mailing list address@hidden 
>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>> 
>> 
>> _______________________________________________ Discuss-gnuradio
>> mailing list address@hidden 
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTz65pAAoJEBQ6EdjyzlHtFoYH/1cmvi9j4BBKlV1NeypGtsQv
XukSmNQJ2gqFSrQvBt3xjVB/5BZYTj4VOkj86hSTr2hn0IucaG81JYt1v/FyN5rM
1rRblVUtyaWuGnN2gREuoGT8jn6GsSFmztHlp6LUj2ZxkCbWAO27fzurT35Bd3Fy
koTQxxF5vxxgtMuoL0/KV2M1znqT84OrHB3V8fuKudKjmp4r3QzgaLtOYLRxlm7b
g7DHLZ4us+8hFaXzUb6rgS+BHDJlic47JsinUCYMIX1QVV//qSg89lZM/n5YqG67
ODdzcs7CGA7c1aWXgFVnfJT5kpJ2oA65X4TglC24OEfnyffKyxkJln56mQ+Jsvk=
=ALg0
-----END PGP SIGNATURE-----