While I agree that it is not practical for everyone to release (or more aptly re-release) all BAIN ready packages - the dialogue piece that you might be missing is team FCOM basically telling me to stuff it and other general insults.
It got to the point that I'd see thread after thread of people asking 'how do I install FCOM?' and then FCOM team members would climb all over these new guys and say 'why aren't you posting in the FCOM thread?' And general berating of questions for not RTFM. Then look at FCOM where most of the parts are in the hands of a very few people who can control how it is packaged, but opt to keep 3 different install methods (by hand, exe, and if using 3rd party scripts OMOD). They and many other modders can take the the couple of hours required to learn how to package a BAIN package and release it so that this overhaul (that already requires Wrye Bash) can utilize BAIN to provide a uniform install method and thereby greatly reduce the number of questions and confusions and in turn reduce the number of posts about why people aren't posting in one place.
Granted Dev_Akm is long gone and we all get busy - I understand that, but really what does it take to just check in for 5 minutes and make a post. Francesco did that and so did Oscuro at one point. Francesco gave permission for repackaging and whatever a few months ago. So my conclusion is that with the FCOM example it is self-induced and until they get it together to make a central location for information and a uniform method of installing all the component parts they get what they ask for (a lot of confusion on the mod user end). Ultimately it is none of my business except that I too don't like useless 5 post threads asking what has been asked 1000 times before. I removed all previous examples of how to BAIN FCOM.
Other things I've read are that Bash is way to complicated to ask of the average user, that modders would rather not have to worry about how a mod is packaged, that BAIN is too new and so on. Well BAIN has been around for about 2 years and I know I wrote http://www.gamesas.com/index.php?/topic/957424-custom-bain-projects/ on it almost two years ago. It is ready to go with Morrowind, Oblivion, both Fallout games, and now Nehrim too. I can think of many instances where modders went back and repackaged with OMODs and scripted installs but no not with BAIN even though it would be easier. I can also think of many instances where mods were repackaged as OMODs by other people and uploaded. The only instance I can think of with BAIN is http://tesnexus.com/downloads/file.php?id=22170. He really wanted to promote the new installer as something to encourage modders to adapt to and really this is what these two threads have been about. Carrying on that intention.
What I find interesting is knowing the few modders on here that I've had opportunity to chat with and such - those that prefer to do manual installing end up making the most thorough BAIN ready packages. Better packaging upon release is what leads to less noob questions by the user.[/end rant]
Alright back on topic with what is practical. I'm curious what you mean by subpackaging hackish behavior. I recall Wrye really thinking that through and have done so a lot myself. Here is a comprehensive HGEC BAIN package I have is the EVE for FCOM package:
Spoiler EVE Compilation-BAIN ├[00 EVE Stock Replacer Core] ├[01 Body Textures] ├[10 EBE E-Cup nvde] ├[10 EBE E-Cup Underwear] ├[10 Normal C-Cup nvde] ├[10 Normal C-Cup Underwear] ├[10 Normal E-Cup nvde] ├[10 Normal E-Cup Underwear] ├[15 Lowerbody EBE nvde] ├[15 Lowerbody EBE Underwear] ├[15 Lowerbody Normal nvde] ├[15 Lowerbody Normal Underwear] ├[15 Lowerbody Wide nvde] ├[15 Lowerbody Wide Underwear] ├[20 Equipment Replacer Upperbody - EBE E-Cup] ├[20 Equipment Replacer Upperbody - Normal C-Cup] ├[20 Equipment Replacer Upperbody - Normal E-Cup] ├[21 Equipment Replacer Upperbody - Normal C-Cup Alt] ├[25 Equipment Replacer Lowerbody - EBE] ├[25 Equipment Replacer Lowerbody - Normal] ├[25 Equipment Replacer Lowerbody - Wide] ├[30 ---- FCOM EVE Core -----Use with FCOM--] ├[40 ---- OOO EVE Core -------Plus one of the following] ├[41 OOO Equipment Replacer Upperbody - EBE E-Cup] ├[41 OOO Equipment Replacer Upperbody - Normal C-Cup] ├[41 OOO Equipment Replacer Upperbody - Normal E-Cup] ├[42 OOO Equipment Replacer Lowerbody - EBE] ├[42 OOO Equipment Replacer Lowerbody - Normal] ├[42 OOO Equipment Replacer Lowerbody - Wide] ├[50 ---- FRANS EVE Core ----Plus one of the following] ├[51 FRANS Equipment Replacer Upperbody - EBE E-Cup] ├[51 FRANS Equipment Replacer Upperbody - Normal C-Cup] ├[51 FRANS Equipment Replacer Upperbody - Normal E-Cup] ├[52 FRANS Equipment Replacer Lowerbody - EBE] ├[52 FRANS Equipment Replacer Lowerbody - Normal] ├[52 FRANS Equipment Replacer Lowerbody - Wide] ├[60 ---- MMM Eve Core -----Plus one of the following] ├[61 MMM Equipment Replacer Upperbody - EBE E-Cup] ├[61 MMM Equipment Replacer Upperbody - Normal C-Cup] ├[61 MMM Equipment Replacer Upperbody - Normal E-Cup] ├[62 MMM Equipment Replacer Lowerbody - EBE] ├[62 MMM Equipment Replacer Lowerbody - Normal] ├[62 MMM Equipment Replacer Lowerbody - Wide] ├[70 ---- Armamentarium EVE Core ----Plus one of the following] ├[71 ARMA Equipment Replacer Upperbody - EBE E-Cup] ├[71 ARMA Equipment Replacer Upperbody - Normal C-Cup] ├[71 ARMA Equipment Replacer Upperbody - Normal E-Cup] ├[72 ARMA Equipment Replacer Lowerbody - EBE] ├[72 ARMA Equipment Replacer Lowerbody - Normal] ├[72 ARMA Equipment Replacer Lowerbody - Wide] ├[80 ---- Artifacts EVE Core ----Plus one of the following] ├[81 Equipment Replacer Upperbody - EBE E-Cup] ├[81 Equipment Replacer Upperbody - Normal C-Cup] ├[81 Equipment Replacer Upperbody - Normal E-Cup] ├[82 Equipment Replacer Lowerbody - EBE] ├[82 Equipment Replacer Lowerbody - Normal] ├[82 Equipment Replacer Lowerbody - Wide]
Notice that if the packages are exclusive of each other they have the same number. That is precisely what Wrye advised doing. If they are not exclusive then use different alpha-numeric naming of sub-packages. Actually Roberts male is much more difficult to translate:
Spoiler Roberts Male 4-BAIN ├[00 Roberts Male v4 Core] ├[01 Beautiful People Compatibility] ├[05 Optional Idles] ├[06 Human Head] ├[07 Orc Head] ├[08 Better Necklines] ├[10 Average nvde BASE] ├[11 Average Cothed - Pants 1] ├[11 Average Cothed - Pants 2] ├[11 Average Cothed - Pants 3] ├[20 Muscular nvde BASE] ├[21 Muscular Clothed - Pants 1] ├[21 Muscular Clothed - Pants 2] ├[21 Muscular Clothed - Pants 3] ├[21 Muscular Clothed - Pants 4] ├[21 Muscular Clothed - Pants 5] ├[22 Muscular Sandals] ├[30 Slender nvde BASE] ├[31 Slender Clothed - Pants 1] ├[31 Slender Clothed - Pants 2] ├[31 Slender Clothed - Pants 3] ├[40 Breeze Defined Male Body - nvde] ├[41 Breeze Defined Male Body - clothed] ├[41 BreezeVascularBody - Breton] ├[41 BreezeVascularBody - Dark Seducer] ├[41 BreezeVascularBody - Darkelf] ├[41 BreezeVascularBody - Dremora] ├[41 BreezeVascularBody - Golden Saint] ├[41 BreezeVascularBody - Highelf] ├[41 BreezeVascularBody - Imperial] ├[41 BreezeVascularBody - Nords] ├[41 BreezeVascularBody - Orcs] ├[41 BreezeVascularBody - Redgaurds] ├[41 BreezeVascularBody - Woodelf] ├[45 GhogielDefinedMaps for Roberts Male] ├[46 Durza Roberts male v4 - less muscular for Slender] ├[50 Roberts Average Stock Clothes and Armor] ├[50 Roberts Muscular Stock Clothes and Armor] ├[51 Roberts Muscular FCOM Armor]
Mostly because of how it was originally packaged with alternate versions buried in the meshes and textures with alternate names and folders. Even actually already is much easier to package.
Do you have a better suggestion for sub-package logic?
Either way repackaging is simpler when many many are going to request it. Why I advocate requesting or making your own packages is really detailed in my opening posts. Haven't changed my mind on it. The philosophical approach is to automate what one would be doing by hand and therefore a promotion of the manual installing mindset. I'm not arguing against the creation or development of wizards or BCF - I just won't use them much.