Simple Package Creation: Difference between revisions
Appearance
m Added categories and screen shot for the initial package list. |
No edit summary |
||
| Line 24: | Line 24: | ||
** Name must contain the name used to apt-get install the package. | ** Name must contain the name used to apt-get install the package. | ||
** Repository Source should be Ubuntu/Package | ** Repository Source should be Ubuntu/Package | ||
** Repository should be intrepid | ** Repository should be | ||
***intrepid main (for 0810) | |||
***lucid main (for 1004) | |||
** Hit Save | ** Hit Save | ||
** Hit Add other compatibility | ** Hit Add other compatibility | ||
*** Select Linux and Ubuntu Intrepid/Linux | *** Select Linux and | ||
**** Ubuntu Intrepid/Linux (for 0810) | |||
**** Ubuntu Lucid/Linux (for 1004) | |||
*** Hit Save | *** Hit Save | ||
* Hit Save & Close | * Hit Save & Close | ||
= sqlCVS = | = sqlCVS = | ||
After adding the package to your local pluto_main database, you have to commit this definition to the main sqlCVS. Before committing it (or better, before diffing and checking in), do a sqlCVS update for all tables in the DCE repo. The sqlCVS diff should also be made for all tables in the DCE repo only. | After adding the package to your local pluto_main database, you have to commit this definition to the main sqlCVS. Before committing it (or better, before diffing and checking in), do a sqlCVS update for all tables in the DCE repo. The sqlCVS diff should also be made for all tables in the DCE repo only. | ||
Latest revision as of 05:55, 27 July 2012

This article outlines how to create a simple package to reference an external deb for dependency sake. These packages are needed, in case a LinuxMCE package depends on it, or a device template needs to have the package installed.
Details
This recipe contains the steps that are needed. If a field or drop down is not mentioned, it is NOT needed!
First form
- In the web admin go to Advanced/Software/Packages and click Create Package
- Description should be a meaning full name, that people can understand (free form text)
- PackageType is helpful to define what it is (but is not needed)
- Manufacturer is important. Leave it empty. Do NOT put Pluto in there. See the original Packages page for details.
- Hit Save & Close
Second form
- Package compatibility
- Operating System must be Linux
- Packages this depends on
- Select whatever other package this new package depends on and click add (add as many or as little as you like). You do not need to add any at all.
- Sources for package
- Hit Add other Source
- Name must contain the name used to apt-get install the package.
- Repository Source should be Ubuntu/Package
- Repository should be
- intrepid main (for 0810)
- lucid main (for 1004)
- Hit Save
- Hit Add other compatibility
- Select Linux and
- Ubuntu Intrepid/Linux (for 0810)
- Ubuntu Lucid/Linux (for 1004)
- Hit Save
- Select Linux and
- Hit Save & Close
sqlCVS
After adding the package to your local pluto_main database, you have to commit this definition to the main sqlCVS. Before committing it (or better, before diffing and checking in), do a sqlCVS update for all tables in the DCE repo. The sqlCVS diff should also be made for all tables in the DCE repo only.