[Soul_Est]

Originally Posted by boggsie

I think an interesting approach would be to create the ROM as a bare, or with a minimum of items and then cook the CABs of the available applications into the ROM and finally, cook Tier Autoinstall into the ROM so that the first time the ROM boots up, the user has the ability to select which CABs they install.

So, the base you select can be customized each and every time it is installed and is only limited by the number of combinations of installable CABs that you build into the base.

Thanks boggsie for that great ideas. It made me think of implementing something you'd normally see in Unix-like operating systems: software repositories. Think pacman for Arch Linux or apt for Debian. I'll definitely look into Tier's AutoInstall and Paul's AppToDate to see what they can do for the user.

Originally Posted by jakdillard

This project sounds very familiar ........... Hmmmmm

Originally Posted by No1ustad

haha. i was thinking the same thing

You're both right. These were just ideas I was throwing out there to gather interest and see how popular they would be. Thanks for the input.

I'm currently working on ironing the bugs out of a ROM I'm building for helping with developing OEMs. I'll release that ROM this week under the codename RL (RegistryLogger). AppToDate and UC are slated for the next version of this ROM. Once I figure out a way to get the two to work together like pacman or apt, users and developers would also have the option of not using their computers for everything except flashing a new bootloader, radio or producing software or ROMS.