[Pkg-xen-devel] A bit of tagging

Ralph Passgang ralph at debianbase.de
Fri Feb 17 19:26:58 UTC 2006


Am Freitag, 17. Februar 2006 19:18 schrieb Guido Trotter:
> On Fri, Feb 17, 2006 at 05:48:53PM +0100, Ralph Passgang wrote:
[...]
>> your right, I didn't knew that we would need to supply a manpage for every 
>> executable, even if the executable is not really meant to be a "user-tool".
>> 
>
> Well, the thought is that if it's not meant to be a user-tool then /usr/bin 
> is the wrong place for it... It should probably reside in /usr/lib/xen 
> perhaps! 

some of them are indeed:

/usr/lib/xen/bin/qemu-dm.debug
/usr/lib/xen/bin/xc_restore
/usr/lib/xen/bin/xenconsole
/usr/lib/xen/bin/xenctx
/usr/lib/xen/bin/xc_save
/usr/lib/xen/bin/qemu-dm


> > (I think we will have this bug open for ever, because it's hard to write
> > manpages for tools that haven't got any kind of documentation in
> > upstream).
>
> Well, we could stop distributing executables that are not useful, or move
> them away, if the user never needs to call them! :)

no, you got me a bit wrong. these tools (or at least the most) are not 
useless, but the "normal" user will never have to use them in normal 
operation, because xend (and other scripts) call them internal or because of 
the fact that this file are just for developer/debugging stuff.

for example xen3 stores domain related information in a system called 
"xenstore". The user normaly doesn't want to add a network card via the 
xenstore binaries, because there is an xm command for adding another network 
interface which is easier to use and the only really documented way to do 
this kind of stuff. but xm/xend will call the xenstore binaries internally.

so I don't know if we should move them or not... but at least moving all of 
those files makes the packaging not easier.

for example the vmxloader for vt-enabled systems will have another filename in 
xen 3.0.2 (because they added svm support (amd pacafica) in the unstable-tree 
lately).

at the moment it's ok, because my .install file matches the whole path, but if 
we patch upstream then we have to modifiy those patches often. xen3 is quite 
stable (for my experience as stable as xen 2.0.7 was) but is still changing.

Ian Pratt said that he want a stable xen3 release every six weeks, but I don't 
believe that. But even if we have  a new release all two or three month (with 
always some changes) then we might not want to have to much patches that 
might break then.

> Guido
>
> _______________________________________________
> Pkg-xen-devel mailing list
> Pkg-xen-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-xen-devel



More information about the Pkg-xen-devel mailing list