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