Hi! On Sat, May 29, 2010 at 02:10:43PM +0200, Oliver Schmidt wrote: > However > > .include > .incbin > > seem to behave as before, which means they only find their target > files relative to the current directory. Is this intended this way? Yes. It's currently only the C compiler that has the new code. > I thought I had learned that changes done "semi-automatically" trigger > a rebuild right away? No, there is no automatic build triggered by changes. Sometimes I do that manually. The nightly build checks for any changes since the last build, so there will only be a new nightly build if something in the source tree has changed. > But I've never really understood it. Actually there is not much to understand. A rebuild is triggered every night, but the build script (posted here some time ago) checks for changes since the last build and aborts if there are none. The effect is that there will be a new snapshot package built the night after changes have been made to the source tree. > And I'm not clear about the meaning of the last digit (which is typically > '1'). It is a "build number". RPM packages use it to distinguish builds from the same sources. I'm using it (very rarely) to given the second build on one day a separate number. > Maybe you could write a short Wiki article about the snapshot build > policy (and numbering scheme) ? I doubt that all this is important. Most people don't use the snapshots and those that do don't download a package every day, so the numbers (besides the date) are actually meaningless for them. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat May 29 14:46:56 2010
This archive was generated by hypermail 2.1.8 : 2010-05-29 14:47:00 CEST