Quote:
Originally Posted by rstoyguy
As it is, my current oem collection I transfered to the user_oem directory is 92 megs, packaging it helps me maintain hdd space, clutter, and it will also help me in distributing my rom templates. And the 92 megs compressed down to 26 megs... I also have a couple "sets" of the same OEM's (rguid too) with different skins/regedits so I can easily seperate stuff for a couple different roms.
|
Wait...so you keep it in .rar form all the time? You need to explore the Compress setting in your folder properties. Having multiple copies of the same OEM in different archives...that is a maintenance nightmare. I suggest you explore breaking your .rars up a little so that you don't have the same OEM in two places.
Quote:
|
The 4 megapacks I did were 13 megs, compressed they were 5 megs. Saving precious space on my laptops hdd. I would eventually have had to delete the old kitchens, my music or save space this way...work, yes, but it helped me.
|
Delete all that work stuff. It gets in the way of your cooking anyway
Quote:
|
And when I release a decent/stable/skinned rom and share my work, I can have folks just unrar an archive into the kitchen directory and it will place the selections.txt file and the version_oem.rar into the correct directories and that'll be a lot less work for them. I don't mind working, I dig this stuff!
|
.rar is unquestionably the way to distribute. It's just a poor way of developing.
Quote:
Originally Posted by boggsie
In my case, this was the easiest and most straightforward method to get items to show up where I wanted in the start menu. I extract the OEM from PPCGeeks_OEM.RAR and into the USER_OEM folder. I change the guid (*.rar & *.rgu) and update the option.xml with the new guid and change the group to boggsie and checked to true.
|
Why are you changing the guid? You need to break some old habits.
Quote:
|
I had also tried to manage start menu location via provxml ... I put all of the move, copy, delete file operations into _setup.xml and put that into a cab and ran it as part of sdconfig.txt customizations. The problem there is that the process is very fragile. If a shortcut isn't there or is not named exactly right, the entire cab fails to install.
|
There really isn't a great way of handling this, but there are better ways. The best way would be to not have the start menu locations in the wrong place to start with...