This was actually discussed several times before, and have always been interesting disucssions.

From a usability stand-point, it is both good and bad to add full source to personalized repo. It is good, because you don't need to manually navigate through to find the package you want on the website (search can help with that to some extent: Touch Toolset - Search Packages ), but it is bad because you now have everything from that source in your installer, and you'd need to flick through some times pages and pages of packages to find the one package that you want.

From a server resources point of view, it adds a lot of overhead when checking sources, and adds a package. Take for example Ste Packaging. It is litterally the largest repository, with over 272 packages, everyone would be interested to have at least something on there. As of right now, we have just over 1300 users; if even just 10% of the users request to have the entire repository added to their repo, when the crawler running in the background keeping track of new packages and what not runs, it needs to update 130 users' records. I am sure as we proceed on with more feature developments, and better success with Apple selling more iPod Touch / iPhones, we'll see even more users, which will just make the resource requirements even more ridiculous.

As result of both of the above reasons, a simpler compromise is temporarily put in place. This is the recently introduced RSS feed system. When you're on repo.sc sections (you'll notice "/repo.sc/" as part of the URL), you have extra RSS feed options available -- one if you're not logged in, for updates and additions of all packages on our service; two if you're logged in, an extra one for just updates on packages you've selected. These RSS feeds can be added to the Mobile RSS program, and you can visit the site quickly to the updates page, where you can login (if you've not already done so) and tap the add package option.

In the future, after the small "break" from development I'm having -- as mentioned here: No updates in next week or two. -- and after I am done developing the social components, I have planned for webapp version of the site, where you can easily manage your packages directly from your iPod Touch / iPhones, too.

Bare in mind that I'm still a post secondary student -- this excuse will be gone soon as I'm graduating in a few months -- and don't have the resources like Google, I cannot possibly do absoultely everything. As such, I believe that the compromise of coming to website and update your repo once every now and then is a reasonable trade-off to ease off the 5, 10, or even upwards to 20 to 40 minutes wait just to start off Installer