Re: Re: when to split a package into architecture: all and architecture: any halves

Personally I base my splitting on lintian's warning. The package has a significant amount of architecture-independent data (over 4MB, or over 2MB and more than 50% of the package) in /usr/share but is an architecture-dependent package. This is wasteful of mirror space and bandwidth since it m

Re: when to split a package into architecture: all and architecture: any halves

On Mon, May 24, 2010 at 9:10 PM, Jon Dowland wrote: > I have a package of bup - a git-based backup tool - sitting in the NEW > queue. bup is 99% python, with a small .so module for some > speed-critical code. > > I decided to have an architecture: all bup-common package for the > majority of the

when to split a package into architecture: all and architecture: any halves

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a package of bup - a git-based backup tool - sitting in the NEW queue. bup is 99% python, with a small .so module for some speed-critical code. I decided to have an architecture: all bup-common package for the majority of the program, and