Installing on a new platform - Revision history

Ray N at 17:20, 24 August 2009

2009-08-24T17:20:57Z

←Older revision		Revision as of 17:20, 24 August 2009
Line 1:		Line 1:
			[[Category: Development]]
	In addition to LinuxMCE's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs LinuxMCE needs to run. Because it would be too cumbersome to install all of them by hand, LinuxMCE developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.		In addition to LinuxMCE's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs LinuxMCE needs to run. Because it would be too cumbersome to install all of them by hand, LinuxMCE developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.

Marie.o at 17:24, 21 October 2008

2008-10-21T17:24:17Z

←Older revision		Revision as of 17:24, 21 October 2008
Line 1:		Line 1:
	In addition to LinuxMCE's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs LinuxMCE needs to run. Because it would be too cumbersome to install all of them by hand, LinuxMCE developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.		In addition to LinuxMCE's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs LinuxMCE needs to run. Because it would be too cumbersome to install all of them by hand, LinuxMCE developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.

	The process is fully automated under Linux (Ubuntu), which is LinuxMCE's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly easy task because 90% of the work is handled by the platform-independent back-end hosted on LinuxMCE.~~com~~. In fact, the Ubuntu-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.		The process is fully automated under Linux (Ubuntu), which is LinuxMCE's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly easy task because 90% of the work is handled by the platform-independent back-end hosted on LinuxMCE.org. In fact, the Ubuntu-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.

	If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://www.linuxmce.~~com~~/index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Ubuntu script is ConfirmDependencies_Ubuntu.sh.		If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://www.linuxmce.org/index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Ubuntu script is ConfirmDependencies_Ubuntu.sh.

	Then there is the issue of the package names. Most distros use package names similar to Ubuntu, but there are not always the same. You can look at this file: http://LinuxMCE.~~com~~/download/stdpackages.txt to see all the package names in Ubuntu. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Ubuntu name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.		Then there is the issue of the package names. Most distros use package names similar to Ubuntu, but there are not always the same. You can look at this file: http://LinuxMCE.org/download/stdpackages.txt to see all the package names in Ubuntu. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Ubuntu name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.

	You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Ubuntu.sh) will be specific to Ubuntu. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.		You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Ubuntu.sh) will be specific to Ubuntu. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.

Zaerc: Added "www.linuxmce.com/" to the broken link, not sure what it's doing there tho

2007-06-30T16:43:25Z

Added "www.linuxmce.com/" to the broken link, not sure what it's doing there tho

←Older revision		Revision as of 16:43, 30 June 2007
Line 3:		Line 3:
	The process is fully automated under Linux (Ubuntu), which is LinuxMCE's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly easy task because 90% of the work is handled by the platform-independent back-end hosted on LinuxMCE.com. In fact, the Ubuntu-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.		The process is fully automated under Linux (Ubuntu), which is LinuxMCE's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly easy task because 90% of the work is handled by the platform-independent back-end hosted on LinuxMCE.com. In fact, the Ubuntu-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.

	If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Ubuntu script is ConfirmDependencies_Ubuntu.sh.		If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://www.linuxmce.com/index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Ubuntu script is ConfirmDependencies_Ubuntu.sh.

	Then there is the issue of the package names. Most distros use package names similar to Ubuntu, but there are not always the same. You can look at this file: http://LinuxMCE.com/download/stdpackages.txt to see all the package names in Ubuntu. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Ubuntu name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.		Then there is the issue of the package names. Most distros use package names similar to Ubuntu, but there are not always the same. You can look at this file: http://LinuxMCE.com/download/stdpackages.txt to see all the package names in Ubuntu. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Ubuntu name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.

	You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Ubuntu.sh) will be specific to Ubuntu. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.		You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Ubuntu.sh) will be specific to Ubuntu. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.

Juliet at 09:55, 19 March 2007

2007-03-19T09:55:17Z

←Older revision		Revision as of 09:55, 19 March 2007
Line 5:		Line 5:
	If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Ubuntu script is ConfirmDependencies_Ubuntu.sh.		If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Ubuntu script is ConfirmDependencies_Ubuntu.sh.

	Then there is the issue of the package names. Most distros use package names similar to Ubuntu, but there are not always the same. You can look at this file: http://LinuxMCE.com/download/stdpackages.txt to see all the package names in Ubuntu. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the ~~Debian~~ name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.		Then there is the issue of the package names. Most distros use package names similar to Ubuntu, but there are not always the same. You can look at this file: http://LinuxMCE.com/download/stdpackages.txt to see all the package names in Ubuntu. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Ubuntu name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.

	You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Ubuntu.sh) will be specific to Ubuntu. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.		You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Ubuntu.sh) will be specific to Ubuntu. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.

Jerry finn at 09:10, 19 March 2007

2007-03-19T09:10:04Z

←Older revision		Revision as of 09:10, 19 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>In addition to LinuxMCE's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs LinuxMCE needs to run. Because it would be too cumbersome to install all of them by hand, LinuxMCE developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.		In addition to LinuxMCE's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs LinuxMCE needs to run. Because it would be too cumbersome to install all of them by hand, LinuxMCE developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.

	The process is fully automated under Linux (Ubuntu), which is LinuxMCE's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly easy task because 90% of the work is handled by the platform-independent back-end hosted on LinuxMCE.com. In fact, the Ubuntu-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.		The process is fully automated under Linux (Ubuntu), which is LinuxMCE's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly easy task because 90% of the work is handled by the platform-independent back-end hosted on LinuxMCE.com. In fact, the Ubuntu-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.

Juliet at 12:06, 15 March 2007

2007-03-15T12:06:10Z

←Older revision		Revision as of 12:06, 15 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>In addition to ~~Pluto~~'s own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs ~~Pluto~~ needs to run. Because it would be too cumbersome to install all of them by hand, ~~Pluto~~ developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.		<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>In addition to LinuxMCE's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs LinuxMCE needs to run. Because it would be too cumbersome to install all of them by hand, LinuxMCE developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.

	The process is fully automated under Linux (~~Debian Sarge~~), which is ~~Pluto~~'s native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly ~~eash~~ task because 90% of the work is handled by the platform-independent back-end hosted on ~~plutohome~~.com. In fact, the ~~Debian~~-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.		The process is fully automated under Linux (Ubuntu), which is LinuxMCE's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly easy task because 90% of the work is handled by the platform-independent back-end hosted on LinuxMCE.com. In fact, the Ubuntu-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.

	If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The ~~Debian~~ script is ~~ConfirmDependencies_Debian~~.sh.		If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Ubuntu script is ConfirmDependencies_Ubuntu.sh.

	Then there is the issue of the package names. Most distros use package names similar to ~~Debian~~, but there are not always the same. You can look at this file: http://~~plutohome~~.com/download/stdpackages.txt to see all the package names in ~~Debian~~. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Debian name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.		Then there is the issue of the package names. Most distros use package names similar to Ubuntu, but there are not always the same. You can look at this file: http://LinuxMCE.com/download/stdpackages.txt to see all the package names in Ubuntu. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Debian name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.

	You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ~~ConfirmDependencies_Debian~~.sh) will be specific to ~~Debian~~. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.		You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Ubuntu.sh) will be specific to Ubuntu. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.

Wikiadmin at 02:19, 28 August 2006

2006-08-28T02:19:58Z

←Older revision		Revision as of 02:19, 28 August 2006
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>		<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>In addition to Pluto's own software, it uses lots of other software, like Xine, Asterisk, MythTV, etc. Each has its own set of requirements, like Apache, PHP, MySql. In the end, there are actually hundreds of packages or software programs Pluto needs to run. Because it would be too cumbersome to install all of them by hand, Pluto developed a database-driven, platform-independent installation system. The database back-end tracks all of the software and what other software it needs to work. For example, the database knows that if you want to run our Bluetooth Dongle on Linux, you need Bluez, which requires x and y, which requires z, etc., and on Windows it requires other libraries.
	<p>In addition to Pluto's own software, it uses lots of other software,
	like Xine, Asterisk, MythTV, etc. Each has its own set of requirements,
	like Apache, PHP, MySql. In the end, there are actually hundreds of
	packages or software programs Pluto needs to run. Because it would be
	too cumbersome to install all of them by hand, Pluto developed a
	database-driven, platform-independent installation system. The database
	back-end tracks all of the software and what other software it needs to
	work. For example, the database knows that if you want to run our
	Bluetooth Dongle on Linux, you need Bluez, which requires x and y,
	which requires z, etc., and on Windows it requires other libraries.~~</p><p>The~~
	~~process is fully automated under Linux (Debian Sarge), which is Pluto's~~
	~~native environment. We will also have a fully automated version for~~
	~~Windows soon. If you want to add support for another platform,~~
	~~particularly another Linux distro, this should be a fairly eash task~~
	~~because 90% of the work is handled by the platform-independent back-end~~
	~~hosted on plutohome.com. In fact, the Debian-specific installation~~
	~~script is only about 100 lines in a bash file. If you know some~~
	~~scripting, it will probably be easier to write a new bash file for your~~
	~~distro than to install all the packages by hand.</p><p>If you want to~~
	~~write an installation script, an easy way to start is by checking out~~
	the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Debian script is ConfirmDependencies_Debian.sh.</p><p>Then
	~~there is the issue of the package names. Most distros use package names~~
	~~similar to Debian, but there are not always the same. You can look at~~
	~~this file: http://plutohome.com/download/stdpackages.txt to see all the~~

	~~in a spreadsheet or editor. If you add a column next to the Debian name~~

	~~someone here put those names in the database. If there are more~~

	~~database accordingly. Once we upload it, then the installation script~~

	~~see from our ConfirmDependencies_Script that the wrapper passes in the~~
	~~package name, the source, the repository name, the version, etc. It~~
	~~also passes in the type: get from package, download as a tar, get from~~

	~~ConfirmDependencies_Debian.sh) will be specific to Debian. Other Linux~~
	~~distros should be able to use the same "get from tar", "get from svn",~~
	~~etc. scripts that we wrote for Debian. We provided separate scripts to~~
	~~download from http/ftp, etc. to make this easier. If you send us your~~
	~~revised package list, and a "get from package" version of your script,~~
	~~we will put on our site.</p>~~

			The process is fully automated under Linux (Debian Sarge), which is Pluto's native environment. We will also have a fully automated version for Windows soon. If you want to add support for another platform, particularly another Linux distro, this should be a fairly eash task because 90% of the work is handled by the platform-independent back-end hosted on plutohome.com. In fact, the Debian-specific installation script is only about 100 lines in a bash file. If you know some scripting, it will probably be easier to write a new bash file for your distro than to install all the packages by hand.

			If you want to write an installation script, an easy way to start is by checking out the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Debian script is ConfirmDependencies_Debian.sh.

			Then there is the issue of the package names. Most distros use package names similar to Debian, but there are not always the same. You can look at this file: http://plutohome.com/download/stdpackages.txt to see all the package names in Debian. It's just a tab delimited file, you can use it in a spreadsheet or editor. If you add a column next to the Debian name with the names of the corresponding packages in your distro, we'll have someone here put those names in the database. If there are more packages, or less, just make a note, and we'll adjust the master database accordingly. Once we upload it, then the installation script for your distro will be available in the New Installation Wizard.

			You'll see from our ConfirmDependencies_Script that the wrapper passes in the package name, the source, the repository name, the version, etc. It also passes in the type: get from package, download as a tar, get from svn, etc. Only the 'get from package' (which is ConfirmDependencies_Debian.sh) will be specific to Debian. Other Linux distros should be able to use the same "get from tar", "get from svn", etc. scripts that we wrote for Debian. We provided separate scripts to download from http/ftp, etc. to make this easier. If you send us your revised package list, and a "get from package" version of your script, we will put on our site.

Wikiadmin: Imported document

2006-06-05T16:45:14Z

Imported document

New page

<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>
In addition to Pluto's own software, it uses lots of other software,
like Xine, Asterisk, MythTV, etc. Each has its own set of requirements,
like Apache, PHP, MySql. In the end, there are actually hundreds of
packages or software programs Pluto needs to run. Because it would be
too cumbersome to install all of them by hand, Pluto developed a
database-driven, platform-independent installation system. The database
back-end tracks all of the software and what other software it needs to
work. For example, the database knows that if you want to run our
Bluetooth Dongle on Linux, you need Bluez, which requires x and y,
which requires z, etc., and on Windows it requires other libraries.The
process is fully automated under Linux (Debian Sarge), which is Pluto's
native environment. We will also have a fully automated version for
Windows soon. If you want to add support for another platform,
particularly another Linux distro, this should be a fairly eash task
because 90% of the work is handled by the platform-independent back-end
hosted on plutohome.com. In fact, the Debian-specific installation
script is only about 100 lines in a bash file. If you know some
scripting, it will probably be easier to write a new bash file for your
distro than to install all the packages by hand.If you want to
write an installation script, an easy way to start is by checking out
the source code from our svn or cvs server. http://index.php?section=document&docID=101. Look in the directory ConfirmDependencies_Script. The Debian script is ConfirmDependencies_Debian.sh.Then
there is the issue of the package names. Most distros use package names
similar to Debian, but there are not always the same. You can look at
this file: http://plutohome.com/download/stdpackages.txt to see all the
package names in Debian. It�s just a tab delimited file, you can use it
in a spreadsheet or editor. If you add a column next to the Debian name
with the names of the corresponding packages in your distro, we�ll have
someone here put those names in the database. If there are more
packages, or less, just make a note, and we�ll adjust the master
database accordingly. Once we upload it, then the installation script
for your distro will be available in the New Installation Wizard.You�ll
see from our ConfirmDependencies_Script that the wrapper passes in the
package name, the source, the repository name, the version, etc. It
also passes in the type: get from package, download as a tar, get from
svn, etc. Only the �get from package� (which is
ConfirmDependencies_Debian.sh) will be specific to Debian. Other Linux
distros should be able to use the same "get from tar", "get from svn",
etc. scripts that we wrote for Debian. We provided separate scripts to
download from http/ftp, etc. to make this easier. If you send us your
revised package list, and a "get from package" version of your script,
we will put on our site.