Start work on 0.5.3
prime-xconfig: properly format hexadecimal parameters

Fixes LP: #1252667
debian/postrm.in, debian/rules: avoid calling dpkg-architecture

Fixes LP: #1264611
Release 0.5.3
Start work on 0.5.4
debian/preinst.in: do not touch lightdm.conf any more on anything newer than Precise

Also remove any previous lightdm.conf that nvidia-prime might have messed up.

90-nvidia.conf now contains the relevant settings for PRIME.
Major packaging clean-up

The variable in debian/rules and in templates have clearer names now
debian/preinst.in: clean up the old configuration file that we used to ship in /etc
Release 0.5.4
Start work on 0.5.5
debian/rules: fix path to lightdm configuration files
Release 0.5.5
Start work on 0.5.6
prime-xconfig: format the BusID string correctly

The BusID string created by prime-xconfig had several problems:

1) It was missing the bus type "PCI", as recommended by xorg.conf(5).
2) Values were written in hexadecimal, as reported by lspci, instead
   of decimal, as expected by the server. (See the comment at the top
   of xf86ParsePciBusString().)
3) The PCI domain was not specified.

Giving the BusID string in the wrong format could cause the X server
to fail to parse the BusID, or to parse numbers in the wrong base.
On systems with more than one PCI domain, `lspci -n` output would
include the domain number, which is omitted by default on systems
with only one PCI domain. nv_get_id() expects the bus number to be
the first field, which would not be correct when `lspci -n` reports
the domain, as it does on systems with multiple domains.

Fix these issues by always reporting the domain with `lspci -Dn`
and using it in the BusID string, prepending "PCI:" to the BusID
string, and printing all numeric values in decimal.

Signed-off-by: Daniel Dadap <ddadap@nvidia.com>
Reviewed-by:   Aaron Plattner <aplattner@nvidia.com>
Reviewed-by:   Robert Morell <rmorell@nvidia.com>
Release 0.5.6