* Add 'multilib-testing' to the CSS class list to hide for [multilib]
* Select 'Only In Both' by default, which is probably the most useful option
* Unselect 'Minor Version Mismatches' by default
Signed-off-by: Dan McGee <dan@archlinux.org>
We're getting to the point where we are starting to have a good chunk of JS
scattered about. Centralize a lot of it for maintenance and performance
purposes.
Signed-off-by: Dan McGee <dan@archlinux.org>
This is done as client-side JS which makes the page nice and fast. Minor
versions can be excluded, as can packages in [multilib]. In addition,
architecture filtering is in place so you can limit the subset of shown
packages to those in any, both, one or the other.
Signed-off-by: Dan McGee <dan@archlinux.org>
Anything that it makes sense to add it to gets the treatment here. Anything
with pagination can wait as that will be tougher. We also need to deal with
odd/even formatting.
Signed-off-by: Dan McGee <dan@archlinux.org>
Implements FS#20416. Port over the architecture differences view from
archlinux.de and reimplement in Django with our DB schema. Also use a far
simpler SQL query to do the dirty work rather than the triple UNION
operation. This is accomplished by doing a bit more of the fetching work in
code once we know what packages are actually involved.
Signed-off-by: Dan McGee <dan@archlinux.org>
