Bug 65775 - cerbero: can't use customized "remotes" for *-static.recipes
Summary: cerbero: can't use customized "remotes" for *-static.recipes
Status: ASSIGNED
Alias: None
Product: GStreamer SDK
Classification: Unclassified
Component: General (show other bugs)
Version: 2012.11
Hardware: Other All
: medium minor
Assignee: bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-15 06:08 UTC by cee1
Modified: 2013-06-16 15:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description cee1 2013-06-15 06:08:28 UTC
gst-ffmpeg-static.recipe
"""
class Recipe(custom.GStreamerStatic):
  remotes = {'origin' : 'git://192.168.1.5/gstreamer-sdk/gst-ffmpeg'}
"""
Here, specifies a customized "remotes" for gst-ffmpeg, but this doesn't work, because it's overwritten in custom.py:
"""
class GStreamerStatic(recipe.Recipe):
  ...
  def prepare(self):
    ...
    self.remotes = {'upstream': 'git://anongit.freedesktop.org/gstreamer/%s'
                        % self.project_name}
"""
Comment 1 Andoni Morales Alastruey 2013-06-15 15:36:44 UTC
You can always so something:

def prepare(self)
    super(custom.GStreamerStatic, self).prepare()
    remotes = {'origin' : 'git://192.168.1.5/gstreamer-sdk/gst-ffmpeg'}
Comment 2 cee1 2013-06-16 01:11:34 UTC
(In reply to comment #1)
> You can always so something:
> 
> def prepare(self)
>     super(custom.GStreamerStatic, self).prepare()
>     remotes = {'origin' : 'git://192.168.1.5/gstreamer-sdk/gst-ffmpeg'}
Yes, that works, just one trivial mistake -- should be "self.remotes = ..."

Though, it's inconsistent with the document(http://docs.gstreamer.com/display/GstSDK/Multiplatform+deployment+using+Cerbero).

IMHO, it would be preferred if custom.py respects the manually set "remotes".
Comment 3 Andoni Morales Alastruey 2013-06-16 15:39:12 UTC
Sure,that needs to be fixed properly. I was only suggesting a workaround but I didn't not expressed it correctly :)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.