On Sat, Feb 23, 2013 at 2:45 AM, Alan Bateman <alan.bate...@oracle.com>wrote:
> On 23/02/2013 10:29, David Holmes wrote: > >> >> Just be aware there's a lot more involved in doing this than just >> changing one a name in a makefile. >> >> You beat to me too! Yes, there are likely a lot of scripts and paths > that assume the image name is j2sdk-image or j2re-image so renaming will be > a bit disruptive. > > Sure, but you are *already* making a huge disruptive change to build directory layout. People have to change their scripts from linux-amd64/j2sdk-image to linux-x86_64-normal-server-release/images/j2sdk-image Especially the repetition of "image" seems wrong in the new layout. Why not images/j2sdk-image to images/jdk If you really want to keep "j2sdk-image", move it back into its parent directory. > Also I think the initial goal of the new build system was to get it to the > point where it generated the "same bits" as the old build. I assume this is > why the new build went for the same directory names as the old build (and > probably because of scripts depending on the name too). Hopefully the new build system will lead to an increase, not decrease, in overall sanity.
