Moblin Package Creator Tips and Tricks

Auto-save functionality

MPC can automatically save information input in the GUI for each project.
When you click the "Quit" button, it will ask you if you'd like to save the
params you input. If you click "Yes", next time when you start MPC for the
same project, it will load the save parameters to the GUI.

Preview control/spec file

If you want to add some extra tags or scripts in the rpm spec or deb control file, you can
select "Preview spec file" or "Preview control file" in the "Build control" tab or you can use the "--review-spec/--review-control" option in command line
MPC will wait until you save your changes and continue to build the package

Auto detection

MPC can detect some information for creating package. For example,
package names, versions, authors , dependencies and so on. Please feel free to
edit these detected information

MPC detects package name by using the basename of the selected project root directory,
it will also tries to standardize the package name according to the package name
convention of Debian and rpm packaging policy

MPC detects version number by checking the config.log file. That means you should have a ./configure script in your project.

MPC detects dependencies by using dpkg-shlibdeps (for deb) and find-requires(for rpm).

MPC will detect the packge names according to the SDK you selected. For example, if you choose Moblin2.1 SDK, it will use the database in the SDK to look for depended packages. If no SDK is chosen, it will use the host system to detect dependencies.

MPC detects authors from AUTHORS file in the project

MPC detects copyright from source code

License & copyright

Debian packaging policy requires a copyright file located in /usr/share/doc/moblin-package-creator/. Fields in the "License Details" tab are used to generate this file. MPC will then package this file with other files of your project. Please make sure this file is in the package and the information in it is correct.
The "License" field in the "License Details" tab has a drop down list which contains most commonly used open source licenses. If the license your project needed is not in the list, you can type the name directly in the field.