|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Questions about Xen qemu-dm so I can finish my Debian packag
Hi,
By default in xen-config-host.h, there is:
#define DEFAULT_NETWORK_SCRIPT "/etc/xen/qemu-ifup"
why isn't it:
#define DEFAULT_NETWORK_SCRIPT "/etc/xen/scripts/qemu-ifup"
and can it be changed in the Git to be like this by default? Or should I
patch it in my package?
Also, I asked the following, and still got no answer about it:
1- What is qemu-nbd-xen for, and do I need to package it (together with
its manpage)? Should it go in /usr/bin?
2- Is there anything else than qemu-dm, or qemu-img-xen, that needs to
be present in this package?
3- By default, the xen-setup script does:
./configure --disable-gfx-check --disable-curses \
--disable-slirp "$@" --prefix=/usr
but I saw in the help of ./configure that there is:
--audio-drv-list
that can have the value oss alsa sdl esd pa fmod. I really believe that
OSS support only is not a good idea, and that ALSA, Pulse Audio, SDL and
ESD support would be good. Are they activated by default?
4- Is this normal, and could it be avoided:
dpkg-shlibdeps: warning: dependency on libm.so.6 could be avoided if
"debian/xen-qemu-dm-3.4/usr/lib/xen-3.4/boot/qemu-dm" were not uselessly
linked against it (they use none of its symbols).
dpkg-shlibdeps: warning: dependency on libXext.so.6 could be avoided if
"debian/xen-qemu-dm-3.4/usr/lib/xen-3.4/boot/qemu-dm" were not uselessly
linked against it (they use none of its symbols).
I really need these answers before the upload of my Debian package, that
by the way, works already.
Thomas
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Questions about Xen qemu-dm so I can finish my Debian packaging,
Thomas Goirand <=
|
|
|
|
|