Ubuntu
xserver-xorg-video-ati package

How to split source code xf86-video-ati in Ubuntu ati and radeon packages?

Asked by Terac

I've downloaded from here
http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/snapshot/xf86-video-ati-6.10.0.tar.bz2
and correctly compiled the source code "xf86-video-ati" on my Ubuntu 8.10 64 bit.

I used checkinstall utility and when the compiling process ended It gave me a .deb file that include ati (the wrapper) and radeon (the driver). It works fine and I've successfully updated my radeon drivers from version 6.9.0 to version 6.10.0 obtaining full benefit from the new xvideo vsync function included in the latest version.

It works for me on my system, but if I want to share those drivers with other people I'd like to compile packages in a "compliant" way with Ubuntu policy.
Ubuntu Canonical choice for ati open driver actually is to split the wrapper and the driver from the source code and separate them in two packages:
- xserver-xorg-video-ati <--- for the wrapper
- xserver-xorg-video-radeon <--- for the driver

How can I split the source code in two subcode myself in order to compile them separately and obtain two packages redistributables? Or how can I do two differents compiling process from the same source and obtain two packages?

Thank you in advance!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu xserver-xorg-video-ati Edit question
Assignee:
No assignee Edit question
Solved by:
Terac
Solved:
Last query:
Last reply:
Revision history for this message
Tom (tom6) said : 		#1

I'm not sure if there's help near the end of this trouble-shooting guide on sound generally?

http://alsa.opensrc.org/index.php/TroubleShooting

Please let us know
Regards from
Tom :)

Revision history for this message
Christopher Lunsford (binarymutant) said : 		#2

if you need an example of how it's done in the official repositories just:
apt-get source xserver-xorg-video-ati

As far as I can tell they use the debian/control file to split the source into different packages. Hope that helped

Revision history for this message
Terac (scatterd-deactivatedaccount) said : 		#3

Thank you for your answers!
I' ve just discovered that checkinstall tool simply ignores the debian folder and its control file.
In that file I've found the settings for every packages but it seems checkinstall simply does not read these.

I've simply replaced checkinstall with debuild that actually does the compiling process the proper way, as intended in the debian package build policy.

Thank you again!

Revision history for this message
Tom (tom6) said : 		#4

You're welcome - nicely fixed

Regards from
Tom :)