On Sun, Nov 13, 2005 at 06:18:36PM +0100, Sven Luther wrote:
> Ah, i was going to not parse anything and just copy it as is into INITRD_CMD.
> Mmm, wait, i forgot something, this is not the usecase i want, what i want is 
> :
> ramdisk: mkinitrd.yaird mkinitramfs
> the list of actual binaries being called, not the dependencies. No versions in
> sight for this, and the full value need to be overridable globaly, per arch,
> per subarch or per flavour.

This needs a reverse-lookup to generate the dependencies.

The following includes any information to build both dependencies and
the list of executables without hardcoding any piece of information.
| [base]
| image-ramdisk-generators: initramfs-tools
| 
| [relations]
| initramfs-tools: bla
| 
| [image-ramdisk-generators]
| initramfs-tools: mkinitramfs

I'm not sure about the linux-initramfs-tool part of the dependency.

Bastian

-- 
Time is fluid ... like a river with currents, eddies, backwash.
                -- Spock, "The City on the Edge of Forever", stardate 3134.0

Attachment: signature.asc
Description: Digital signature

Reply via email to