| 1 |
On Tue, 2 Sep 2014 22:38:56 Jc García wrote: |
| 2 |
> 2014-09-02 22:07 GMT-06:00 Saifi Khan <saifikhan@×××××××××××.org>: |
| 3 |
> > . how 'inherits eutils java-vm-2 prefix versionator' line works. what |
| 4 |
> > exactly does 'inherits' clause/function do ? |
| 5 |
> |
| 6 |
> Read the development documentation if you plan to tweak ebuilds, |
| 7 |
> replicating it here is just a lost of time, a hint, is about using |
| 8 |
> eclasses. |
| 9 |
|
| 10 |
'inherit' loads eclasses into the ebuild, setting up the environment and |
| 11 |
making functions for given scenarios availble. See [0] for reference. |
| 12 |
|
| 13 |
> > . where is the function 'get_version_component_range' defined ? |
| 14 |
> |
| 15 |
> Likely in the versionator eclass. |
| 16 |
|
| 17 |
It is a function in the eclass - see [0] and [1]. |
| 18 |
|
| 19 |
> > Additionally, how do i get 'emerge' to ignore/suppress the 'missing |
| 20 |
> > digest' |
| 21 |
> > for a given ebuild ? |
| 22 |
> |
| 23 |
> When you read the documentation you will learn to test your ebuilds |
| 24 |
> and generating manifests, a hint, learn about repoman and a local |
| 25 |
> portage or overlay to tweak ebuilds |
| 26 |
|
| 27 |
There are two methods here: |
| 28 |
a) to create a local overlay and regenerate the manifest with each change |
| 29 |
b) to use the 'ebuild' utility to test each of the specific ebuild stages |
| 30 |
|
| 31 |
When maintaining a repository of ebuilds locally, it's better to use an |
| 32 |
overlay (see [2]), however it's generally easier when working on a single |
| 33 |
ebuild to simply call the ebuild functions explicitly (allowing testing of |
| 34 |
specific stages of the build) - see [3] or, better, `man ebuild`. |
| 35 |
|
| 36 |
> > Thanks in advance. |
| 37 |
> |
| 38 |
> That said since it's for a minor release the ebulid you want to bump, |
| 39 |
> the changes to the ebuild might be just the file name, and some |
| 40 |
> version related strings in the ebuild, but I'm too noob with ebuilds |
| 41 |
> to be sure about this. Also you can do a bug report requesting for the |
| 42 |
> bump, just search first in the bug-tracker it hasn't been done yet. |
| 43 |
|
| 44 |
Yes, often minor package changes can be handled by simply changing the ebuild |
| 45 |
name, however this requires that the ebuild was written properly, using such |
| 46 |
variables as ${PV} to substitute the version as determined by the ebuild name, |
| 47 |
rather than hard-coding the version into the ebuild (like setting SRC_URI to |
| 48 |
"http://blah/blah/package-${PV}.tgz" rather than ".../package-1.2.3.tgz" ). |
| 49 |
|
| 50 |
As has been suggested, give it a try, poke around, and if you get something |
| 51 |
working, feel free to attach it to the bug report (subtle hint here ;-) ) to |
| 52 |
help move things along. |
| 53 |
|
| 54 |
[0] http://devmanual.gentoo.org/eclass-reference/index.html |
| 55 |
[1] http://devmanual.gentoo.org/eclass-reference/versionator.eclass/index.html |
| 56 |
[2] https://wiki.gentoo.org/wiki/Overlay/Local_overlay |
| 57 |
[3] http://dev.gentoo.org/~zmedico/portage/doc/man/ebuild.1.html |
| 58 |
|
| 59 |
-- |
| 60 |
wraeth |
Archives