* GOTO Masanori wrote: > Hmm, I don't know the detail of udeb framework - well, it seems we > have to change -udeb package name for each archs. But... I don't > still know that this udeb naming framework is really > well-thought-out things? Are there any standard rule of udeb > package naming scheme? I would like to know it before changing > package name.
There are rules how an udeb must be structured, what it may contain and what ist must not contain. You can find them in the documentation of the debian installer: http://cvs.debian.org/debian-installer/doc/ Specifically the file modules.txt is of interest. However, when working on the gtk frontend I came into touch with many libraries that had to be packaged as udebs, and found that this aspect was not well covered so far. I talked to some developers and then write a proposal set of rules of what is important for library udebs. You can find it here http://lists.debian.org/debian-boot/2003/debian-boot-200303/msg00036.html It is far from being complete, and I would be glad if you had something to add, or propose some changes. Discussion takes place on debian-boot. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
