Catalogue package naming

Now that I've started working with the mingw-dist catalogue system and
understanding some nuances and such I'm going to suggest something
that will help with affiliate package naming for the GUI.

What I'm thinking is a categorical package naming system.  Using
package foo as an example I'm thinking that we could have a
mingw32-current-foo package a mingw32-previous-foo package and a
mingw32-history-foo package.  The history package would contain all
the packages older than previous.  I am also thinking that we have
package names of mingw32-current-ancillary-foo, etc where the
mingw-current-foo would contain the primary binary files and the
ancillary package would contain the documentation and other
non-required files for the binary package.  By doing this we can
present the user with a better GUI presentation based on the affiliate
grouping.

Thoughts?

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk