open-vm-tools packaging [Was: Re: duplicate hgfs.h, block.h, stubs.h includes in archive....]

[Olivier L. <oli...@ce...>]

Dominique, thanks a lot for your tips.

See my comments below.

> The wiki gives quite some overview of what to package and where to put it.
> Most of the things are done correct by now using make install (I remember a
> time this did not do anything useful).
> http://open-vm-tools.wiki.sourceforge.net/Packaging
Yes, I know this URL, unfortunately, I did not find any usefull tips regarding 
includes and devel parts.
It looks like some .c files are shared between modules and tools, that some .h 
files are in tools build structure, but also used by some mudules

For now I have an open-vm-tools that works for the userlan tools and system.
what I'm stuck with is the foillowing:
- Put modules in a dkms package that build modules at boot if the kernel has 
been updated
- Create a working open-vm-tools-devel package that permit developpements of 
new tools (tuypicaly would contain includes and .so files)

> Maybe you can have a look what I all did in the RPM for openSUSE? Might
Thanks a lot for your help, I had a 1st look at your RPM spec file which looks 
very interresting (see mine attached).
Unfortunately I don't quite understand the module part. As a distribution 
owner I understand that you create a binary package for the modules right?
I assume that %suse_kernel_module_package -n vmware-guest -p %{SOURCE98} xen 
um does all the magic ;-)
Although, I'm unable to follow this way as I'm not a Mandriva developper and 
thus I'm unable to follow thightly all new kernel releases. If a user updates 
its kernel, then I'll loose ability to connect it its vm and I'll have to 
rebuild modules by hand.
Thus I'm forced to go for the dkms way until Mandriva includes open-vm-tools 
in its main release tree.

Maybe one day all thoses modules will go into the standard linux kernel.... 
who knows?

Olivier.
-- 
	Olivier LAHAYE
	CEA Saclay
	DRT-LIST-DETECS-SSTM