Comment #7 on issue 17586 by rosenstand: Generate a source tarball with
each release
http://code.google.com/p/chromium/issues/detail?id=17586
Unfortunately I just found this post after having spent evenings figuring
out how to
reliably produce a perfect release tarball useful for packagers such as
myself. I
imagine this exercise has been practiced by tens of packagers by now,
because of the
lovely customized VCS wrapper and build system. Reminds me of the awful
cdrtools and
its S(ch)illy Makefile system.
This is such a waste of resources - I really hope you guys will show more
love for
Linux packagers in the future.
#5: Instead of writing (and maintaining!) your own bash version of
export_tarball.py,
you can just skip the gclient config step and write your own .gclient,
excluding
whatever causes it to fail. Here's mine:
cat >.gclient <<EOF
solutions = [
{ "name" : "$VERSION",
"url" : "http://src.chromium.org/svn/releases/$VERSION";,
"custom_deps" : {
"src/chrome/app/theme/google_chrome": None,
"src/chrome/installer/linux": None,
"src/chrome/test/data/layout_tests/LayoutTests": None,
"src/chrome/tools/test/reference_build": None,
"src/third_party/WebKit/LayoutTests": None,
"src/webkit/data/layout_tests/LayoutTests": None,
"src/webkit/tools/test/reference_build": None,
},
"safesync_url": ""
}
]
EOF
Some of the excludes are incorrect but shouldn't harm anything. Just built
4.0.288.0
using this method. Also you can use build/gyp_chromium to avoid the gclient
build
dependency, assuming you've already created the tarball.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
