On Mon, Apr 20, 2009 at 12:34 PM, Dennis d'Entremont <dennis.dentremont@xxxxxxxxx> wrote: >> That depends on your usage; if you only use it for full builds anyway, >> it doesn't matter a lot. As soon as you want to update single >> components, though, it becomes mandatory. > > Is the old method going to be discontinued at some point? By discontinued, do you mean untested/unmaintained? It more-or-less is already... as experienced recently with the new create_image rule that caused so many people issues. It mostly affected those who weren't using build profiles. The only reason people continue using the old method, is because the new method isn't documented in the "guides" that are so rampant. You can *replace* these 3 lines: HAIKU_IMAGE_DIR = /dev ; HAIKU_IMAGE_NAME = sda2 ; HAIKU_DONT_CLEAR_IMAGE = 1 ; with a single line: DefineBuildProfile partition2 : disk : "/dev/sda2" ; (note the name you give it is up to you) and then use the following: jam -q @partition2 or if you just want to update a build you already have without wiping the partition (and thus, keeping all apps, settings, data, etc.): jam -q @partition2 update-all I just don't understand why people are loathe to change... - Urias ----------------------------------------------------------------------- haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List