On 2020-07-28 12:02+0200 Ramon Fischer <ramon_fisc...@hotmail.de> wrote:
> Hello tastytea, > > I am aware of this "workaround", thank you. :) > > I guess, I was not precise enough: > > The ebuild "drm_master_util-9999"[1] is hosted on my repository, but > the ebuild file itself pulls in an external repository[2]. Sorry, I misread your first email. > My question is: Is it a best practise to fork the external > repository[2], to link my fork with "drm_master_util-9999"[1], so I > have full control about updating the fork. Just to check, that the > external source is not doing shenanigans? I would use either EGIT_COMMIT from git-r3.eclass¹ or download a snapshot via SRC_URI². ¹ <https://devmanual.gentoo.org/eclass-reference/git-r3.eclass/index.html#lbAF> ² <https://github.com/gch1p/drm_master_util/archive/<COMMIT-HASH>.tar.gz>
