POSTING IN THIS FORUM

[Llorean]

Start a thread in this forum ONLY to announce a new custom build.

If you have questions about a build you found via a thread in this forum, ONLY ASK ABOUT IT IN THAT THREAD.

Builds in this forum are not officially supported. Any time you think you've found a bug in Rockbox, and not just one of these builds, use the "current build" link on the left of the screen to download a new, official copy, and make sure the problem happens there before making an official bug report of it.

Questions about unofficial builds outside of their topics may be deleted without explanation.

All thread topics should be in this format:
Supported Players: Your Name Your Build's Name

Note: This board is sorted Alphabetically so that a user might more easily find a port for their target.

[Llorean]

Small update:

I'm going to start removing builds if they aren't updated for over a month. If you're going to be gone for a period and will not be able to update your build, I will gladly leave the thread until you return, but at this time I feel the most important thing is to try to keep the unsupported builds section trim. I've unlocked this topic in case you want to offer objections or suggestions as to a better way. I'll begin doing this in two days, I believe.

[redwood]

I'm going to start removing builds if they aren't updated for over a month....I've unlocked this topic in case you want to offer objections or suggestions as to a better way.

How about a sub topic archiving the older build threads?

jp

[Yotto]

In case a lot of people chime in and say they don't like the idea, I just want you to know I love it.  Sorted by name instead of date, any new posts off the first page could become lost.

[BigMac]

This is not related to your idea Llorean, but I think it would be nice if builds were requires to have the date they last uploaded on in the title. This I guess would help you out in your removal process, and it would let everyone else know that the build is not from a month old source.

[bascule]

I'm going to start removing builds if they aren't updated for over a month.

Will this policy be reviewed for custom builds based on the 3.0 release (like the ipod accessories build)?

As 3.0 will not be updated once released, it would seem a bit harsh to delete custom builds based on that release.

[Llorean]

For custom builds based on release versions, they'll probably just be removed a short time after the next release comes out.

[soap]

I don't have a good reason why I made the accessory build based on the 3.0 branch.
Really, I don't.

[bascule]

I don't have a good reason why I made the accessory build based on the 3.0 branch.
Really, I don't.

I thought it was a good idea. At least builds based on a release will not get broken so often by other updates. On the other hand, of course, that only applies to patches that are never likely to be accepted into SVN. Unless you split the accessories patch into trunk and 3.0 versions, there will be some sort of a mess, somewhere.