Perryg wrote:While I can not speak of how to do this with "the debian way", I do know that the official way to build the package is to do so using the VirtualBox build process and not the hosts.
Example: running the following
- Code: Select all Expand viewCollapse view
/trunk/src/VBox/Installer/linux/debian/rules binary
^^^^^
To clean if you need to rebuild:
- Code: Select all Expand viewCollapse view
/trunk/src/VBox/Installer/linux/debian/rules clean
^^^^^
That works, as long as you have all dependencies installed. To the list you linked above, I added 'zip' which was needed to build the guest additions, IIRC.
klaus wrote:The toplevel debian directory shouldn't be removed, it should be turned into one which directly works again.
If this is not the official way to build it, I don't see the reason why. Why would you need two different ways to build the same package, with the potential of producing two different results or no result at all, as is the case right now? It may be possible to create a working top-level debian directory again, if you adapt the paths. But it will be different from the one under src/VBox/Installer/linux, and every change would have to be carefully kept in sync between the two.
Unneccessary work, if you ask me. I'd put the Instructions from PerryG plus the right apt-get line in a top-level README or INSTALL file, and that's it. It took me most of the time to find this out, because the broken top-level debian fooled me into thinking this was the 'official' way to build the package.