On Wed, 19 Feb 2014 17:05:09 +0100, Roelof Wobben <r.wob...@home.nl>
wrote:
> Hello,
> 
> I have updated a ebuild to a new version.
> 
> Am I right I have to make a local repo to test if it's build.
> And does ebuild x.ebuild  manifest also builds the package or do I
> have to use emerge x for that.
> 
> And for testing Is repoman scan enough after looking if the package
> can installed of course.
> 
> I have looked into the manuals but I cannot find a clear answer.
> 
> Roelof
> 
> 
> ---
> Dit e-mailbericht bevat geen virussen en malware omdat avast!
> Antivirus-bescherming actief is. http://www.avast.com
> 
> 
`ebuild ... manifest` only downloads the files listed in SRC_URI of the
ebuild and creates/updates the file 'Manifest' in the same directory as
the ebuild file. The same can also be accomplished by running `repoman
manifest` from the directory containing the ebuild file.

To build the package, you can use emerge like you would for a
main-tree package. This requires you to set PORTDIR_OVERLAY in
make.conf (or your environment) to point to your overlay. It also
requires superuser access for most actions.

Alternatively, you can run individual phases with `ebuild ... $command`
(see ebuild(1) [1] for the right commands for the different phases).
Prerequisite phases are run for most commands, notably excepting
'qmerge'. Dependencies are not automatically installed when using
`ebuild` directly, so you must first make sure they are installed, for
example using `emerge --oneshot --noreplace list of dependencies`.

repoman does not run the code in the /functions/ of an ebuild
(src_configure and so on), but only performs static analysis on them.
Thus, problems arising from actually running the package's build system
can not be caught this way.

You should probably also verify that the stuff that gets installed by
your ebuild actually works before you share it with others, which would
require you to actually build and install it to your system as
described above.

1: https://dev.gentoo.org/~zmedico/portage/doc/man/ebuild.1.html

-- 
eroen

Attachment: signature.asc
Description: PGP signature

Reply via email to