On Tue, 2 Sep 2014 22:38:56 Jc García wrote: > 2014-09-02 22:07 GMT-06:00 Saifi Khan <[email protected]>: > > . how 'inherits eutils java-vm-2 prefix versionator' line works. what > > exactly does 'inherits' clause/function do ? > > Read the development documentation if you plan to tweak ebuilds, > replicating it here is just a lost of time, a hint, is about using > eclasses.
'inherit' loads eclasses into the ebuild, setting up the environment and
making functions for given scenarios availble. See [0] for reference.
> > . where is the function 'get_version_component_range' defined ?
>
> Likely in the versionator eclass.
It is a function in the eclass - see [0] and [1].
> > Additionally, how do i get 'emerge' to ignore/suppress the 'missing
> > digest'
> > for a given ebuild ?
>
> When you read the documentation you will learn to test your ebuilds
> and generating manifests, a hint, learn about repoman and a local
> portage or overlay to tweak ebuilds
There are two methods here:
a) to create a local overlay and regenerate the manifest with each change
b) to use the 'ebuild' utility to test each of the specific ebuild stages
When maintaining a repository of ebuilds locally, it's better to use an
overlay (see [2]), however it's generally easier when working on a single
ebuild to simply call the ebuild functions explicitly (allowing testing of
specific stages of the build) - see [3] or, better, `man ebuild`.
> > Thanks in advance.
>
> That said since it's for a minor release the ebulid you want to bump,
> the changes to the ebuild might be just the file name, and some
> version related strings in the ebuild, but I'm too noob with ebuilds
> to be sure about this. Also you can do a bug report requesting for the
> bump, just search first in the bug-tracker it hasn't been done yet.
Yes, often minor package changes can be handled by simply changing the ebuild
name, however this requires that the ebuild was written properly, using such
variables as ${PV} to substitute the version as determined by the ebuild name,
rather than hard-coding the version into the ebuild (like setting SRC_URI to
"http://blah/blah/package-${PV}.tgz"; rather than ".../package-1.2.3.tgz" ).
As has been suggested, give it a try, poke around, and if you get something
working, feel free to attach it to the bug report (subtle hint here ;-) ) to
help move things along.
[0] http://devmanual.gentoo.org/eclass-reference/index.html
[1] http://devmanual.gentoo.org/eclass-reference/versionator.eclass/index.html
[2] https://wiki.gentoo.org/wiki/Overlay/Local_overlay
[3] http://dev.gentoo.org/~zmedico/portage/doc/man/ebuild.1.html
--
wraeth
signature.asc
Description: This is a digitally signed message part.
