From: Romain Lenglet <rlenglet@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] Xenomai patch packaging concerns
Date: Thu, 23 Feb 2006 12:24:38 +0900 [thread overview]
Message-ID: <200602231224.38519.rlenglet@domain.hid> (raw)
Hi,
I understand that the prepare-kernel.sh script is a kind of
"smart patch" program. It is very nice, but for packaging for
Debian we need a real diff file. So I am currently modifying
prepare-kernel.sh to be even smarter, so that it can optionally
generate a diff file instead of actually modifying the Linux
tree. This is done efficiently in terms of disk space, i.e. it
does not duplicate the Linux tree to generate the diff file.
I will send a patch for prepare-kernel.sh once I have finished.
However, I have a problem: some files are copied (linked) several
times into the Linux tree. As a consequence, in a generated diff
file those files would be duplicated. And I believe that such a
duplication is unecessary.
Here are the sets of links that are currently made by
prepare-kernel.sh (on every line: Linux tree -> Xeno tree):
1- arch/<arch>/xenomai/* -> ksrc/arch/<arch>/*
2- kernel/xenomai/* -> ksrc/*
3- kernel/xenomai/arch/* -> ksrc/arch/<arch>/*
4- kernel/xenomai/drivers/*... -> ksrc/drivers/*...
5- kernel/xenomai/nucleus/*... -> ksrc/nucleus/*...
6- kernel/xenomai/skins/*... -> ksrc/skins/*...
7- drivers/xenomai/*... -> ksrc/drivers/*...
8- include/asm-<arch>/xenomai/* -> include/asm-<arch>/*
9- include/asm-generic/xenomai/* -> include/asm-generic/*
10- include/xenomai/* -> include/*
11- include/xenomai/asm-<arch>/* -> include/asm-<arch>/*
12- include/xenomai/asm-generic/* -> include/asm-generic/*
...
1- and 3- are redundant: I guess that 3- is not required?
4- and 7- are redundant: I guess that 4- is not required?
8- and 11- are redundant: I guess that 11- is not required?
9- and 12- are redundant: I guess that 12- is not required?
I everybody agrees, I will modify prepare-kernel.sh to not
generate the 3-, 4-, 11- and 12- sets of links.
Note that removing the 3- and 4- sets of links would also require
to modify the ksrc/Makefile file, so that the line:
obj-$(CONFIG_XENOMAI) += arch/ nucleus/ skins/
becomes:
obj-$(CONFIG_XENOMAI) += nucleus/ skins/
and the following line should be suppressed:
subdir-$(CONFIG_XENOMAI) += arch
Is that OK?
It would even be better and easier to modify the Xenomai source
tree to match better the Linux tree:
ksrc/
L arch
L drivers
L kernel
L nucleus
L skins
And I also will make prepare-kernel.sh not link (or generate
diff) for the asm-<arch> and arch/<arch>/ directories for
architectures that are different from the built architecture.
--
Romain LENGLET
next reply other threads:[~2006-02-23 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 3:24 Romain Lenglet [this message]
2006-02-23 15:21 ` [Xenomai-core] Xenomai patch packaging concerns Philippe Gerum
2006-02-24 11:56 ` Romain Lenglet
[not found] ` <17407.3428.428108.146818@domain.hid>
2006-02-25 5:13 ` Romain Lenglet
2006-02-27 9:10 ` Philippe Gerum
2006-02-27 13:55 ` Philippe Gerum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602231224.38519.rlenglet@domain.hid \
--to=rlenglet@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.