Okay, my brain won't shut up.
I had the thought that packages like NHibernate.Example.AspNet or
NHibernate.Full.AspNet could be offered. These combined packages
could have all appropriate dependencies to get up and running in a
particular scenario. The fact of the matter is that the NHibernate
world is so flexible and wide-reaching, that it's hard to pre-decide
on an exact set of packages the user might need. I would think it
would be more clear in the end to have simple packages and then
combine them either through "example" packages or documentation.
Patrick Earl
