- ebuilds for a given package in the specified overlay (defaults to
- "/usr/local/portage"), update the manifest, and even emerge it (together
- with its dependencies) if the user requires it. You need write
- permissions on the directory where Gentoo fetches its source files
- (usually "/usr/portage/distfiles").
+ ebuilds for a given package in the default overlay, updates the
+ manifest, and even emerges it (together with its dependencies) if the
+ user requires it.
+
+ The generated ebuilds are placed into the "perl-gcpanp" category. They
+ favour depending on a "virtual", on "perl-core", "dev-perl" or
+ "perl-gcpan" (in that order) rather than "perl-gcpanp".
+
+OPTIONS
+ You can pass specific options to cpan2dist by using the "--dist-opts"
+ command-line argument followed by a "key=value" pair, where "key" is the
+ option name and "value" is what it is set to. "--dist-opts" can be used
+ several times.
+
+ The valid option "key"s are :
+
+ * "manifest"
+
+ A boolean that indicates whether the Manifest file should be
+ generated by running "ebuild manifest" onto the generated ebuilds.
+
+ Defaults to "yes".
+
+ * "overlay"
+
+ A string formatted as a space-delimited sequence of paths, that
+ lists the different overlays in which existent ebuilds will be
+ looked for.
+
+ Defaults to the value of "PORTDIR_OVERLAY" as returned by "emerge
+ --info" (usually /usr/local/portage).
+
+ * "distdir"
+
+ The directory where "ebuild" expects to find the source tarballs.
+ You need write permissions on this directory.
+
+ Defaults to the value of "DISTDIR" as returned by "emerge --info"
+ (usually /usr/portage/distfiles).
+
+ * "keywords"
+
+ The valid "KEYWORDS" for the generated ebuilds.
+
+ Defaults to the value of "ACCEPT_KEYWORDS" as returned by "emerge
+ --info".
+
+ * "header"
+
+ A chunk of text that is prepended to every ebuild.
+
+ Defaults to the generic Gentoo Foundation header.
+
+ * "footer"
+
+ A chunk of text that is appended to every ebuild.
+
+ Defaults to nothing.
+
+ cpan2dist itself takes other options, most notably :
+
+ * "--buildprereq" generates an ebuild for every dependency, even for
+ those that are already up-to-date. Setting this option is
+ recommended.
+
+ * "--force" forcefully regenerates ebuilds even if they already exist.