stop duplicating example-contents data
Bug #612563 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
checkbox (Ubuntu) |
Fix Released
|
Medium
|
Marc Tardif | ||
Maverick |
Fix Released
|
Medium
|
Marc Tardif |
Bug Description
Binary package hint: checkbox
As part of investigating why the CDs are once again oversized since alpha-2, I discovered that checkbox balooned excessively:
checkbox (Δ 5.9 MB - 0.10: 0.1 MB 0.10.1: 6.0 MB)
This is because it started shipping copies of data files which we already have (mostly) in example-contents. This is a major waste, and we should just add a dependency to example-contents instead.
Changed in checkbox (Ubuntu): | |
importance: | Undecided → Medium |
Changed in checkbox (Ubuntu Maverick): | |
milestone: | none → ubuntu-10.10-beta |
Changed in checkbox (Ubuntu Maverick): | |
assignee: | nobody → Jeff Lane (bladernr) |
To post a comment you must log in.
There were some valid reasons for not using example-contents as a dependency for the checkbox tests that require data similar to the ones in question.
The biggest one being, IMHO, the need to not depend on example data that could arbitrarily change, or disappear altogether in the future. Another being the need for file names that make sense from a testing perspective: SongTitle- ArtistName. oga is not a useful description for test output while OggVorbisAudio.oga is.
Also, the structure of the ./data dir in Checkbox was changed to accommodate sorting the various sample file types by category (Audio, Video, Documents, Web) so we could have tests simply parse a directory and tests against the types it finds in there. This allows us to run smaller test sets targeted against specific types or applications (e.g. we can run a batch test against common video types, or common Document types).
One thing I noticed, however, is that the Alpha 2 isos have an version of Checkbox that is not current with trunk. The current trunk has full directory structure and descriptive file types (including types that aren't part of example-content) and was created to satisfy the requirements of the consumer test list project for certification. I'm assuming the current tree has the latest checkbox trunk and will appear in Alpha 3 and beyond.
So for now, the decision made is to move all the data and associated tests from Checkbox to Checkbox- compatibility and that should be accomplished prior to the Beta spin.Bug Description