discuss-gnuradio
[Top][All Lists]
Advanced

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

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


From: Tim
Subject: Re: [Discuss-gnuradio] PyBombs install maint branch from fresh
Date: Wed, 23 Jul 2014 08:36:57 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

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:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTz5xzAAoJEBQ6EdjyzlHt2oYIAJYYair2p3bJqiYwIMVhtX21
O5DUUVV06LQpEXUbxs99JBeGtA4KoY1KddVW2OPx26yUhP49xBAYO8dbNHth4ft8
PHNjS2vWroGK/8otLM8kkdzr+2+YmCw9zMKW/q/nl/afxsdUmu8N+gY9hZYsBkv8
jF8A4UPk7b8d4r79WxHmiiYHN6FLnW9glfGXDbigJMXyERzNaKJVPoy/o9Z7o5Q7
MLjsWBOkikn6mlNFjXD2VrHRBOJwQrp6gRLtirDhMqaeKepD1QBZddWYv5I5vYB0
5U/DFTN7j3Ar/BXWYiFIGFeUPqFunIw4YO6m/e9z4Le5VuJ0H36d3OptieuS/dE=
=twiT
-----END PGP SIGNATURE-----

_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio




reply via email to

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