Trimming bzr package size

[John Ferlito]

On Tue, Jun 09, 2009 at 08:32:06AM -0500, John Arbash Meinel wrote:
> > I've tried to split tests out of bzrlib. This is hard but possible.
> > But without nested trees it's not very good idea, IMO.
> 
> I think that comes down to creating reasonable packaging scripts, rather
> than trying to do it as part of bzr itself.
> 
> Basically, you take the tarball we create as part of the 1.15 release
> and then:
> 
> mv bzrlib/tests ../bzr-tests
> mv doc ../bzr-doc
> 
> Then package what is left of bzr, and then create a package for
> 'bzr-tests' and 'bzr-doc'.
> 
> There would probably need to be a few updates to the core of bzrlib to
> avoid 'from bzrlib.tests import X' in a few places. (cmd_selftest comes
> to mind, but I think a lot of the TransportServer code uses test suite
> fixtures.)
> 
> Though I also thought that part of building packages was to run the
> program's test suite, and I'm not sure how that works with ripping out
> the test suite...
> 
> So if someone wants to put forth the effort, I think it would be okay to
> have a bzr-doc and a bzr-test.

I've already grabbed the bug in launchpad and next release I intend to
modify the packages to create a bzr-doc package.

I'll leave bzr-test for some further discussion here first.

Cheers,
John


-- 
John
Blog                        http://www.inodes.org/blog
OLPC Friends                     http://olpcfriends.org