Gentoo Development: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
** {$S}: Path to the temporary build directory. | ** {$S}: Path to the temporary build directory. | ||
** {$P}: Package name and version. | ** {$P}: Package name and version. | ||
* ebuild myebuild-1.0.ebuild digest will create the manifest for you. It must be able to access the distribution file. If the SRC_URI does not work yet, put the distfile in /usr/portage/distfiles directly. | |||
== Java Ebuild writing guide == | == Java Ebuild writing guide == | ||
Revision as of 12:29, 21 May 2007
- If you write a simple ebuild, you still have to place it in the main Portage tree or in an overlay.
- Apparently you don't get the auto-resume feature automatically. Nor do you get MD5 verification.
General Ebuild development guide
- A list of important variables available when writing ebuilds:
- {$S}: Path to the temporary build directory.
- {$P}: Package name and version.
- ebuild myebuild-1.0.ebuild digest will create the manifest for you. It must be able to access the distribution file. If the SRC_URI does not work yet, put the distfile in /usr/portage/distfiles directly.
Java Ebuild writing guide
- ANT_TASKS can be set (and should be set) manually on the ebuild, but only in src_compile() or src_test().
- The jar names should not contain version number, if you need to rename them, there is an eclass for that: java-pkg_newjar.
- If a package provides differents APIs, the package should be always SLOTed based on the version of the API.