Extracting platform code base prior to cupcake
17 views
Skip to first unread message
sandy8531
Dec 22, 2008, 11:01:35 PM12/22/08
to Repo and Gerrit Discussion
Now that cupcake has been merged to master, how do I get the code base
that is currently shipped with and installed on G1.
When I executed the following, it got me all the cupcake changes.
repo init -u git://android.git.kernel.org/platform/manifest.git
and
repo sync
Is there some revision number that corresponds to the G1 code base ?
I tried the following two revision tags but evidently they are not
correct.
repo init -u git://android.git.kernel.org/platform/manifest.git -b
android-1.0
repo init -u git://android.git.kernel.org/platform/manifest.git -b
release-1.0
that is currently shipped with and installed on G1.
When I executed the following, it got me all the cupcake changes.
repo init -u git://android.git.kernel.org/platform/manifest.git
and
repo sync
Is there some revision number that corresponds to the G1 code base ?
I tried the following two revision tags but evidently they are not
correct.
repo init -u git://android.git.kernel.org/platform/manifest.git -b
android-1.0
repo init -u git://android.git.kernel.org/platform/manifest.git -b
release-1.0
sandy8531
Dec 23, 2008, 12:52:40 AM12/23/08
to Repo and Gerrit Discussion
I must have done something wrong the first time around. The following
worked to get the older code:
Now the question remains, what would I need to do to get code that
corresponds to a currently running build number on the G1 ?
-thanks.
Shawn Pearce
Dec 23, 2008, 10:34:33 AM12/23/08
to repo-d...@googlegroups.com
On Mon, Dec 22, 2008 at 21:52, sandy8531 <math...@gmail.com> wrote:
The branch the G1 is built from hasn't been exported back out to Git since the initial open source release. Recent changes are all merged down into cupcake, and are available in the open cupcake branch, but they aren't broken out from the cupcake specific changes. Right now I know of no plans to re-export the 1.0 branch, because that is effectively in maintenance mode and all activity is on cupcake.
Now the question remains, what would I need to do to get code that
corresponds to a currently running build number on the G1 ?
sandy8531
Dec 23, 2008, 12:58:54 PM12/23/08
to Repo and Gerrit Discussion
On Dec 23, 9:34 am, Shawn Pearce <s...@google.com> wrote:
Oh that is unfortunate. It is incredibly useful for application
developers to get access to production builds and their ability to
simulate bugs and work through problems.
If it is not getting exported to Git, can the production source,
alternatively, be made available in a read only mode, e.g. it gets
pushed to some public code server post a build. This would allow me
to recreate the customer problem on my test systems.
developers to get access to production builds and their ability to
simulate bugs and work through problems.
If it is not getting exported to Git, can the production source,
alternatively, be made available in a read only mode, e.g. it gets
pushed to some public code server post a build. This would allow me
to recreate the customer problem on my test systems.
Jean-Baptiste Queru
Dec 30, 2008, 2:46:20 PM12/30/08
to repo-d...@googlegroups.com
Being able to run custom-built systems that are very close to a
shipping device would definiteely valuable, but there are two hurdles
that made that impractical or impossible for the G1:
shipping device would definiteely valuable, but there are two hurdles
that made that impractical or impossible for the G1:
-The source code for the underying platform that powers the G1 was not
releasable "as is". The additional amount of work that would have been
necessary there would have gotten in the way of being able to
open-source cupcake. We preferred to get the cupcake tree out so that
the issue would be less likely to re-appear.
-The G1 contains a significant number of proprietary applications,
drivers, etc... that aren't part of the core Android Open-Source
Project. Even if the source code for the 1.0 platform that powers the
G1 was released, you'd still be missing many parts to turn the base
platform into something that exactly matches what shipped on the G1.
Cupcake sets a base that should reduce the impact of the first aspect,
with the open-source tree being hopefully eventually close (or
identical) to the underlying platform of the stuff that ends up on
consumer devices.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.
GTeye
Dec 30, 2008, 5:36:05 PM12/30/08
to Repo and Gerrit Discussion
Am I to understand that the features of cupcake are not going to find
their way onto our Tmobile G1 devices?
Many of us purchased these phones with the understanding that the
google development that was going on to add features to the android
system were going to be put into place for us to use.
It is going to be a very bad start for the android system if G1 users
are left out on these features. Customers are going to be irate and
that is going to trickle down into public perception.
I think if this is the case that an announcement needs to be made asap
so that people can decide what to do with their phones.
On Dec 30, 11:46 am, Jean-Baptiste Queru <j...@google.com> wrote:
> Being able to run custom-built systems that are very close to a
> shipping device would definiteely valuable, but there are two hurdles
> that made that impractical or impossible for the G1:
>
> -The source code for the underying platform that powers the G1 was not
> releasable "as is". The additional amount of work that would have been
> necessary there would have gotten in the way of being able to
> open-source cupcake. We preferred to get the cupcake tree out so that
> the issue would be less likely to re-appear.
>
> -The G1 contains a significant number of proprietary applications,
> drivers, etc... that aren't part of the core Android Open-Source
> Project. Even if the source code for the 1.0 platform that powers the
> G1 was released, you'd still be missing many parts to turn the base
> platform into something that exactly matches what shipped on the G1.
>
> Cupcake sets a base that should reduce the impact of the first aspect,
> with the open-source tree being hopefully eventually close (or
> identical) to the underlying platform of the stuff that ends up on
> consumer devices.
>
> JBQ
>
>
> - Show quoted text -
their way onto our Tmobile G1 devices?
Many of us purchased these phones with the understanding that the
google development that was going on to add features to the android
system were going to be put into place for us to use.
It is going to be a very bad start for the android system if G1 users
are left out on these features. Customers are going to be irate and
that is going to trickle down into public perception.
I think if this is the case that an announcement needs to be made asap
so that people can decide what to do with their phones.
On Dec 30, 11:46 am, Jean-Baptiste Queru <j...@google.com> wrote:
> Being able to run custom-built systems that are very close to a
> shipping device would definiteely valuable, but there are two hurdles
> that made that impractical or impossible for the G1:
>
> -The source code for the underying platform that powers the G1 was not
> releasable "as is". The additional amount of work that would have been
> necessary there would have gotten in the way of being able to
> open-source cupcake. We preferred to get the cupcake tree out so that
> the issue would be less likely to re-appear.
>
> -The G1 contains a significant number of proprietary applications,
> drivers, etc... that aren't part of the core Android Open-Source
> Project. Even if the source code for the 1.0 platform that powers the
> G1 was released, you'd still be missing many parts to turn the base
> platform into something that exactly matches what shipped on the G1.
>
> Cupcake sets a base that should reduce the impact of the first aspect,
> with the open-source tree being hopefully eventually close (or
> identical) to the underlying platform of the stuff that ends up on
> consumer devices.
>
> JBQ
>
> On 12/23/08, sandy8531 <mathur...@gmail.com> wrote:
>
>
>
>
>
>
>
> > On Dec 23, 9:34 am, Shawn Pearce <s...@google.com> wrote:
> >> On Mon, Dec 22, 2008 at 21:52, sandy8531 <mathur...@gmail.com> wrote:
>
> >> > Now the question remains, what would I need to do to get code that
> >> > corresponds to a currently running build number on the G1 ?
>
> >> The branch the G1 is built from hasn't been exported back out to Git since
> >> the initial open source release. Recent changes are all merged down into
> >> cupcake, and are available in the open cupcake branch, but they aren't
> >> broken out from the cupcake specific changes. Right now I know of no
> >> plans
> >> to re-export the 1.0 branch, because that is effectively in maintenance
> >> mode
> >> and all activity is on cupcake.
>
> > Oh that is unfortunate. It is incredibly useful for application
> > developers to get access to production builds and their ability to
> > simulate bugs and work through problems.
> > If it is not getting exported to Git, can the production source,
> > alternatively, be made available in a read only mode, e.g. it gets
> > pushed to some public code server post a build. This would allow me
> > to recreate the customer problem on my test systems.
>
> --
> Jean-Baptiste M. "JBQ" Queru
> Android Engineer, Google.- Hide quoted text -
>
>
>
>
>
>
>
> > On Dec 23, 9:34 am, Shawn Pearce <s...@google.com> wrote:
> >> On Mon, Dec 22, 2008 at 21:52, sandy8531 <mathur...@gmail.com> wrote:
>
> >> > Now the question remains, what would I need to do to get code that
> >> > corresponds to a currently running build number on the G1 ?
>
> >> The branch the G1 is built from hasn't been exported back out to Git since
> >> the initial open source release. Recent changes are all merged down into
> >> cupcake, and are available in the open cupcake branch, but they aren't
> >> broken out from the cupcake specific changes. Right now I know of no
> >> plans
> >> to re-export the 1.0 branch, because that is effectively in maintenance
> >> mode
> >> and all activity is on cupcake.
>
> > Oh that is unfortunate. It is incredibly useful for application
> > developers to get access to production builds and their ability to
> > simulate bugs and work through problems.
> > If it is not getting exported to Git, can the production source,
> > alternatively, be made available in a read only mode, e.g. it gets
> > pushed to some public code server post a build. This would allow me
> > to recreate the customer problem on my test systems.
>
> --
> Jean-Baptiste M. "JBQ" Queru
>
> - Show quoted text -
Robert Barrett
Dec 30, 2008, 5:58:05 PM12/30/08
to repo-d...@googlegroups.com
To be a little fair, Google Android developers never did say the cupcake
was for the G1 but it just seems totally unfair for G1 users.
was for the G1 but it just seems totally unfair for G1 users.
Robert Barrett
2 Corinthians 13:14
The grace of the Lord Jesus Christ, and the love of God, and
the communion of the Holy Spirit be with you all. Amen.
Dave Sparks
Dec 30, 2008, 5:59:08 PM12/30/08
to repo-d...@googlegroups.com
I'm sympathetic to your situation, but this is the wrong forum for this discussion.
FWIW, the Android Open Source Project has no control over the deployment of code on devices. As an analogy, it's a bit like beating the Linux community over the head because Dell won't update the Red Hat distro on your computer.
FWIW, the Android Open Source Project has no control over the deployment of code on devices. As an analogy, it's a bit like beating the Linux community over the head because Dell won't update the Red Hat distro on your computer.
GTeye
Dec 30, 2008, 7:52:04 PM12/30/08
to Repo and Gerrit Discussion
My phone has Google stamped on the back of it so I don't totally
consider it the same thing as your analogy.
Tmobile and Google marketed the G1 together and Tmobile reps are
telling customers that updates will be made available whenever they
are released by google.
When I bought my phone and my wifes, the tmobile rep told us that the
a2dp update and soft keyboard were coming as part of the update and he
even mentioned "cupcake" by name.
I understand you, as android developers, are not personally
responsible for this however you, as android developers you can help
push Tmobile to make this happen simply because it's going to be a PR
nightmare for the android os if tmobile tells its customers, who
purchased this phone on good faith, i'd even go so far as saying as a
favor to be a guinea pig for this new operating system, that they
aren't getting available updates. Being told oh sorry, you'll need
the G2 in order to do that is going ot reflect so poorly not only on
tmobile but on android.
Perhaps, as android developers you could make the transition and
inclusion on the G1 easier for them so that they perhaps may do so.
Android does not need a pissed off community, they need a happy one
and the way the G1 is perceived is going to say alot about the future
success of Android.
> > > - Show quoted text -- Hide quoted text -
consider it the same thing as your analogy.
Tmobile and Google marketed the G1 together and Tmobile reps are
telling customers that updates will be made available whenever they
are released by google.
When I bought my phone and my wifes, the tmobile rep told us that the
a2dp update and soft keyboard were coming as part of the update and he
even mentioned "cupcake" by name.
I understand you, as android developers, are not personally
responsible for this however you, as android developers you can help
push Tmobile to make this happen simply because it's going to be a PR
nightmare for the android os if tmobile tells its customers, who
purchased this phone on good faith, i'd even go so far as saying as a
favor to be a guinea pig for this new operating system, that they
aren't getting available updates. Being told oh sorry, you'll need
the G2 in order to do that is going ot reflect so poorly not only on
tmobile but on android.
Perhaps, as android developers you could make the transition and
inclusion on the G1 easier for them so that they perhaps may do so.
Android does not need a pissed off community, they need a happy one
and the way the G1 is perceived is going to say alot about the future
success of Android.
Dave Sparks
Dec 30, 2008, 8:15:39 PM12/30/08
to repo-d...@googlegroups.com
I'll be happy to continue this discussion on android-discuss if you like. Otherwise, this is my last posting on the topic.
Apologies to the other repo-discuss readers for the digression.
Apologies to the other repo-discuss readers for the digression.
Reply all
Reply to author
Forward
0 new messages