1 |
Hiya, |
2 |
|
3 |
I'm trying to update/package up mypy for the main tree which, whilst it |
4 |
provides a release tarball, relies upon a data library (typeshed) which |
5 |
does not provide releases. The recommended method of installation by |
6 |
upstream is to use git submodules (which the ebuild will do happily), |
7 |
but repoman rightly complains about LIVEVCS issues. |
8 |
|
9 |
Is the current recommended method for dealing with this to manually |
10 |
create a tarball and stash it on dev.gentoo.org somewhere accessible or |
11 |
are there updated guidelines for this kind of scenario? If so, where |
12 |
would they be documented? Searching for LIVECVS found a bunch of |
13 |
repoman change discussions, but no documentation as to how to deal with |
14 |
ebuilds that require this... |
15 |
|
16 |
Mike 5:) |