Difference between revisions of "Porting Raspbian"

Revision as of 04:56, 25 July 2012

This will attempt to highlight some of the requirements/process intended/followed for porting lmce to raspbian for use on the raspberry pi New database data

• update the 'Distro' table, add Raspbian: (then sqlCVS diff/get batch approved/sqlCVS udpate) - Done.

insert into Distro (Description, FK_OperatingSystem, Installer, SourceCode, Confirmed, InstallerURL ) values ('Raspbian Wheezy', 1, 'ConfirmDependencies_Debian.sh', 'src', 1, 'installDebian.php')

• update the 'RepositorySource' table, add the main raspbian repo and an lmce raspbian repo [2 entries]: (then sqlCVS diff/get batch approved/sqlCVS update) - Done.

insert into RepositorySource (FK_OperatingSystem, FK_Distro, FK_RepositoryType, Description, Define, Instructions) values ( 1, 19, 1, 'Raspbian', 'Raspbian', 'This package is part of Raspbian')
insert into RepositorySource (FK_OperatingSystem, FK_Distro, FK_RepositoryType, Description, Instructions) values (1, 19, 1, 'Raspbian LinuxMCE addons', 'LinuxMCE packages for Raspbian')

• update the 'RepositorySource_URL' table, add the URLs for the 2 repositories above [2 entries]: (then sqlCVS diff/get batch approved/sqlCVS update) - Done.

insert into RepositorySource_URL (FK_RepositorySource, URL) values ( 22, 'deb http://archive.raspbian.org/raspbian')
insert into RepositorySource_URL (FK_RepositorySource, URL) values ( 23, 'deb http://deb.linuxmce.org/raspbian')

• Update all the Packages related tables. Linuxmce uses the database at build time when creating deb packages for dependencies and later at install time to install those dependencies, add repositories to /etc/sources.list and so on. Since on every release some packages tend to change names or split/merge into others, updating the packages tables is time consuming and you need to do some install/fix cycles before figuring them all out.
• Conf files update
  • Build dependencies list needs updating. The list with packages needed for building linuxmce needs to be updated from one release to another so you can have the dependencies installed on the build machine. There is no automatic tool for doing this and is a time consuming task when package names change and split as you need to wait for the build to fail to intstall other packages. This could be partially automated.

Other issues:

1. diskless boot? net boot is not immediately possible from RPi, perhaps a netboot after kernel?
2. disked boot? may be required
3. avwizard - graphics setup is performed by gpu prior to the kernel boot. new method of setting/determining graphics mode? changing resolution requires reboot for gpu init
4. qOrbiter
5. omxplayer device template/player
6. arm libs required for pre-compiled libraries (usb-uirt, external media identifier?/id-my-disc?, more?)
7. mythtv frontend is too heavy for RPi, recordings will need to be natively played by omxplayer
8. install scripts for diskless or disked based systems
9. boot scripts