On Sun, Nov 13, 2005 at 04:20:56PM +0100, Bastian Blank wrote: > On Sun, Nov 13, 2005 at 03:50:09PM +0100, Sven Luther wrote: > > I mean we need to find a way to override the k-p's default for ramdisk on a > > per arch/subarch/flavour basis, and a ramdisk= line in the defines seems to > > be > > most obvious place for this. > > I currently try to implement such. My plan is something like: > > arch/defines: > | [base] > | image-ramdisk-generators: initramfs-tools yaird > | > | [relations] > | initramfs-tools: initramfs-tools (>= foo) > > arch/$arch/defines: > | [base] > | image-ramdisk-generators: yaird > > Which makes it possible to generate both the dependencies and the > correct order for each flavour.
Why not : ramdisk: initramfs-tools (>= foo) yaird I mean, the ramdisk: is shorter and thus nicer than image-ramdisk-generators, but more importantly, why the two levels ? Have you planed something else where this is important ? > This may be extended with something like: > arch/defines: > | [relations] > | toolchain-gcc: gcc (>= 4:4.0), binutils (>= foo) > | toolchain-gcc-hppa: %(toolchain-gcc)s, gcc-hppa, binutils-hppa > > To generate the toolchain-builddeps. Nice, Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
