Use the component feature of apt sources to categorize packages.

[mspasov]

My idea is to use the component feature to categorize packages. I (and probably others too) don't use themes and wallpapers (at least not from packages) and it's really useless for me to download and track them. Since wallpapers and themes will outnumber the rest packages, my proposition is to create a policy for categories (and make packagers and repos follow it), however using more than few (5) categories could make things confusing and probably the best way is to add them on the way.

1. main (the current - everything goes in, except:)
2. themes (themes, wallpapers, sounds - everything that is used to change appearance of the device - arch-independent files (i.e. not the software that changes it).
3. hacks - patches/additions to the device itself - localizations, carrier logos and settings, everything that replaces/edits device .plists and is not a standalone software/application itself. (the proposition behid this is because, at least on installer, there were quite large number of fixes and hacks for different regions and carriers).

ps. personally I think that 1. and 2. would be most useful, for the hacks category - I'm not really sure.

Thank you and all kind of comments are welcome.

[saurik]

This is not a good idea because it makes it more difficult to have dependencies. Example: sometimes an application needs a hack, so it Depends: it.

If you want to filter out themes you should use Section/Edit to turn them off. I do not believe this feature was in Cydia when this bug was written (in fact, this bug was written two weeks too soon for that), so I will consider this "fixed" by that enhancement.