1 |
On 2020.07.14 17:05, Jack wrote: |
2 |
> I want to try some changes to an ebuild in the dotnet overlay. So, I |
3 |
> copied /var/lib/layman/dotnet/dev-lang/mono/mono-9999.ebuild into |
4 |
> /usr/local/portage/dev-lang/mono. I cd into that directory, and run |
5 |
> "ebuild mono-9999.ebuild manifest" and it fails because it tries to |
6 |
> download mono-9999.tar.bz2, which obviously doesn't exist anywhere. |
7 |
> There is no SRC_URI in the ebuild, just |
8 |
> "EGIT_REPO_URI="git://github.com/mono/${PN}.git". Also, I notice |
9 |
> there is no Manifest file (or no DIST line) for any 9999 ebuild - and |
10 |
> that seems true in the main tree and also overlays. Trying "ebuild |
11 |
> mono-9999.ebuild prepare" complains that the digest is missing. So |
12 |
> does "emerge mono-9999.ebuild" although it complains that a file (the |
13 |
> ebuild itself) is not listed in the manifest. |
14 |
> |
15 |
> So - if a manifest entry is not needed for a live/9999 ebuild, why is |
16 |
> portage (ebuild or emerge) failing to work without one, and why is it |
17 |
> trying to download a tarball, even without any SRC_URI in the ebuild? |
18 |
> |
19 |
> Jack |
20 |
With some help from #gentoo, it turns out mono-env.eclass in ::gentoo |
21 |
includes a SRC_URI line. That eclass in ::dotnet does not. When I |
22 |
tried a 9999 ebuild in ::local. it used the ::gentoo version of the |
23 |
eclass. Explicitly adding 'SRC_URI=""' after the inherit line in the |
24 |
ebuild fixed it. |