FW this discussion to community.<br><br><div class="gmail_quote">On Thu, Mar 5, 2009 at 5:36 PM, Felipe Contreras <span dir="ltr"><<a href="mailto:felipe.contreras@gmail.com" target="_blank">felipe.contreras@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br> On Thu, Mar 5, 2009 at 11:13 AM, bilboed <<a href="mailto:bilboed@gmail.com" target="_blank">bilboed@gmail.com</a>> wrote:<br> ><br> > Yes, all of the gstreamer modules are in git.<br> ><br> > But here are some pros and cons for moving EVERYTHING into those<br> > repositories.<br> ><br> > Pros:<br> > * We don't have to use several repositories<br> > * We can make sure the auto-generated files are up to date (the same<br> > way we do it for win32)</div></blockquote><div> </div><div>Yes, that what I want to say. <br><br>If we maintain two repo (gst android and gst formal), we have to rebase android repo after desktop release. In addition, we have to merge bug fix, enhancement, performance improvement submitted to android repo back into formal release. It's a tiresome work.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br> ><br> > Cons:<br> > * I don't think it's very wise to be using gstreamer git head<br> > (constantly being developed) for embedded development.<br> <br> </div>Have a 'stable' branch. Note that the name 'branch' is misleading<br> because it would actually be on the same patch as the 'master' branch,<br> except not updated that often. I could point to the last release for<br> example.<br> <div><br> > * The auto-generated files and Android.mk files might need to be<br> > slightly different per target/setup.<br> > * People might not be too keen on having Android-specific files/build<br> > in GStreamer (Android.mk, auto-generated files, etc...)<br> </div></blockquote><div><br>That why I drop all auto generated files into an anroid directory. <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><br> </div>Put them in a separate branch. Debian people would probably not like<br> RPM stuff either, so there could be 'debian' and 'rpm' branches.<br> <br> If GStreamer doesn't want these branches in the official repo, then<br> they will happen in some other repo.<br> <div><br> > After all... it's git, so our repositories will be 'extra remotes'<br> > that you can use with the official gstreamer repositories (and<br> > therefore, you could easily rebase the android-specific branch against<br> > the current git head and give it a try).<br> ><br> > Let's first get some repositories out there, then we'll have a much<br> > clearer picture of what can happen.<br> <br> </div>Yes.</blockquote><div><br>Yes. Good idea.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> <br> --<br> <font color="#888888">Felipe Contreras<br> </font><div><div></div><div><br> --~--~---------~--~----~------------~-------~--~----~<br> You received this message because you are subscribed to the Google Groups "prajnashi" group.<br> To post to this group, send email to <a href="mailto:prajnashi@googlegroups.com" target="_blank">prajnashi@googlegroups.com</a><br> To unsubscribe from this group, send email to <a href="mailto:prajnashi%2Bunsubscribe@googlegroups.com" target="_blank">prajnashi+unsubscribe@googlegroups.com</a><br> For more options, visit this group at <a href="http://groups.google.com/group/prajnashi?hl=en" target="_blank">http://groups.google.com/group/prajnashi?hl=en</a><br> -~----------~----~----~----~------~----~------~--~---<br> <br> </div></div></blockquote></div><br><br clear="all"><br>-- <br>-- Prajnashi S<br>