Editing Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 115: | Line 115: | ||
The Application Manager only shows packages in the user section. Thus, the <code>Section:</code> field in the control file must have the <code>Section: user/<SUBSECTION></code> syntax, where <code><SUBSECTION></code> is arbitrary. See section [localhost#sec:making_app_pack_sections 17.2.6] for information on the suggested values. | The Application Manager only shows packages in the user section. Thus, the <code>Section:</code> field in the control file must have the <code>Section: user/<SUBSECTION></code> syntax, where <code><SUBSECTION></code> is arbitrary. See section [localhost#sec:making_app_pack_sections 17.2.6] for information on the suggested values. | ||
- | Usually you do not have to change the <code>rules</code> file. However, if the new .deb package is empty, check the "install:" section to make sure that the <code>DESTDIR</code> environment variable is pointing to the where the other packaging scripts are looking for the application to be packaged. | + | Usually you do not have to change the <code>rules</code> file. However, if the new .deb package is empty, check the "install:" section to make sure that the <code>DESTDIR</code> environment variable is pointing to the where the other the packaging scripts are looking for the application to be packaged. |
Once the application is properly 'Debianized', building the application is performed easily with the command: | Once the application is properly 'Debianized', building the application is performed easily with the command: |
Learn more about Contributing to the wiki.