Closed GoogleCodeExporter closed 9 years ago
Yeh I really will like this too..
David, what kind of problems did you have when you had the repo set up as git?
Did gclient config work as intended? Could we just nest stuff inside a src/ dir
inside our git repo?
Original comment by danakj@chromium.org
on 4 Mar 2013 at 4:08
I'd like to switch to git too. If we could just have a git repo named "src"
things would work just fine but googlecode doesn't seem to allow that. You
can't really checkout a sub-directory with git so even if somehow possible
that's probably not what we want for easy development.
We could use a different repo name than "src" and you'd need to use gclient
--name=src https://chromium-wm.googlecode.com/git/chromium-wm.git but I don't
like that either.
Best solution might just be to host this where we can name the repo "src".
Original comment by reveman@chromium.org
on 4 Mar 2013 at 4:29
Or maybe instead of telling people to use "gclient config", we just provide a
.gclient file?
Original comment by danakj@chromium.org
on 4 Mar 2013 at 4:49
Looks like it's do-able using Google Code. I tested it out in another repo and
the following seems to work.
Create a git repo (in this case dj2-test-project). Inside that repo I added the
chromium-wm files at the top level. Then:
mkdir dj2-test-project
cd dj2-test-project
git clone https://code.google.com/p/dj2-test-project/ src
gclient config https://dj2-test-project.googlecode.com/src
<edit .gclient to remove large dirs>
gclient sync
cd src
ninja -C out/Debug wm_shell
and everything pulled down correctly and I was able to build wm_shell (well,
with the patch applied, heh).
I was also able to do a git cl upload (after doing a git cl config and
accepting the defaults).
Original comment by dsinclair@chromium.org
on 6 Mar 2013 at 3:39
can you do it without "git clone https://code.google.com/p/dj2-test-project/
src" ?
I'd like the instructions for working on this to be the same as chromium except
that you provide a different url to "gclient config".
Original comment by dreve...@gmail.com
on 6 Mar 2013 at 5:23
This was modeled after the Using Git documentation for Chromium
(https://code.google.com/p/chromium/wiki/UsingGit).
I can see if I can get it to work with the Using New Git
(https://code.google.com/p/chromium/wiki/UsingNewGit) documentation which I
think is closer to what you're looking for.
Original comment by dsinclair@chromium.org
on 6 Mar 2013 at 2:29
And playing with it, I don't think it will work without the name=src as you
commented above. I don't see a way to get it to do the right thing.
Original comment by dsinclair@chromium.org
on 6 Mar 2013 at 2:46
It seems like we'd need to set up our own custom git repo and stuff, and that's
more than I think we want to maintain. I'm okay with modelling this after the
old chromium git workflow.
Original comment by danakj@chromium.org
on 6 Mar 2013 at 5:34
(especially since git cl upload will work!!)
Original comment by danakj@chromium.org
on 6 Mar 2013 at 5:35
code moved to:
https://chromium.googlesource.com/experimental/chromium/src.git
see developer guide for details.
Original comment by reveman@chromium.org
on 19 Aug 2013 at 2:20
Original issue reported on code.google.com by
dsinclair@chromium.org
on 4 Mar 2013 at 2:37