|
Rockbox mail archiveSubject: Re: Branch for updated/initial bootloaders for USB-enabled PP and AMS Sansas (and their installers)Re: Branch for updated/initial bootloaders for USB-enabled PP and AMS Sansas (and their installers)
From: Dominik Riebeling <dominik.riebeling_at_gmail.com>
Date: Thu, 9 Jul 2009 12:30:55 +0200 On Thu, Jul 9, 2009 at 12:16 PM, Paul Louden<paulthenerd_at_gmail.com> wrote: > I'm pretty sure the point is "much like RBUtil, we don't provide current > builds of bootloaders but rather tell people to use individually compiled > builds." Exactly. Plus, I wanted to point out that there *are* alternatives to hard coded values in svn and replacing them with "svn builds" (which does in fact tell nothing, as a release from a (release) branch is, strictly speaking, also an svn build. Calling them "development builds" or "trunk builds" would be more exact). Extending my example of above, you could easily hardcode the version number of the last release to the sources, then tag from that and have the build system always replace the string by the svn revision *except* if some variable is set during compilation (or a target like "make release" is used). You could then keep the hardcoded version number in trunk and still have it in the release tags -- without any changes. Rockbox Utility doesn't use svn revision strings to avoid a dependency on version.sh. - Dominik Received on 2009-07-09 Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy |