I'm working on making a nightly development snapshot of COD to make it easier for folks to work on the Drupal 7 update. Let's download the core tarball instead of grabbing core from git so that we don't get a ton of revision history and a huge tarball.

Comments

ezra-g’s picture

ezra-g’s picture

Title: Grabbing core from Git makes tarball 82MB, haz a sad » Grabbing core/contrib from from Git makes tarball 82MB, haz a sad
Status: Fixed » Needs work

That brought the tarball down to ~42MB ;).

Here are some modules we can consider switching to stable releases to reduce the tarball size:
1.0M features
1.1M views_bulk_operations
1.3M context
1.4M flag
1.7M pathauto
2.0M signup
4.6M commerce
5.2M ctools
6.6M date
18M views

ezra-g’s picture

With cc9580a I switched Views to grab a stable release, which should reduce a further ~17ish MB from the tarball.

greggles’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
japerry’s picture

Status: Needs work » Closed (duplicate)

The build for COD7 I'm using is almost entirely releases instead of git snapshots. There are a few dev versions, but I think in general this should reduce the footprint even further. Right now its sitting at 39M for me.

Marking as a fix in re-roll of D7 located here #1733528: Initial COD D7 Profile D7 and make file

  • Commit cc9580a on 7.x-1.x, pisces by ezra-g:
    Bug #1419446 by ezra-g: Grabbing core from Git makes tarball 82MB, haz a...
  • Commit bd3cf97 on 7.x-1.x, pisces by ezra-g:
    Followup commit to Bug #1419446 by ezra-g: Grabbing core from Git makes...

  • Commit cc9580a on 7.x-1.x, pisces, cod_demo_content by ezra-g:
    Bug #1419446 by ezra-g: Grabbing core from Git makes tarball 82MB, haz a...
  • Commit bd3cf97 on 7.x-1.x, pisces, cod_demo_content by ezra-g:
    Followup commit to Bug #1419446 by ezra-g: Grabbing core from Git makes...