From: Ramon Fischer <Ramon_Fischer@hotmail.de>
To: gentoo-user@lists.gentoo.org
Subject: [SOLVED] Re: [gentoo-user] Ebuild: How to deal with external repositories properly (best practise)?
Date: Sun, 2 Aug 2020 12:51:49 +0200 [thread overview]
Message-ID: <AM6P191MB029625063287B39FB88E23A8EF4C0@AM6P191MB0296.EURP191.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM6P191MB029681155822AAE6AD6D580AEF730@AM6P191MB0296.EURP191.PROD.OUTLOOK.COM>
I decided to use "EGIT_COMMIT" to let the ebuild pulling a certain commit.
Using the archive tarball is indeed interesting!
Thank you for your help!
-Ramon
On 28/07/2020 15:32, Ramon Fischer wrote:
> Oh yeah, as Neil was pointing that out.
>
> I will give it a try and report soon.
>
> -Ramon
>
> On 28/07/2020 14:52, tastytea wrote:
>> On 2020-07-28 12:02+0200 Ramon Fischer <Ramon_Fischer@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>
>>
>
>
next prev parent reply other threads:[~2020-08-02 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 4:47 [gentoo-user] Ebuild: How to deal with external repositories properly (best practise)? Ramon Fischer
2020-07-28 8:53 ` tastytea
2020-07-28 10:02 ` Ramon Fischer
2020-07-28 12:52 ` tastytea
2020-07-28 13:32 ` Ramon Fischer
2020-08-02 10:51 ` Ramon Fischer [this message]
2020-08-04 22:57 ` [SOLVED] " Alexey Mishustin
2020-08-04 23:36 ` Rich Freeman
2020-08-04 23:51 ` tastytea
2020-08-05 0:03 ` Rich Freeman
2020-07-28 10:01 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM6P191MB029625063287B39FB88E23A8EF4C0@AM6P191MB0296.EURP191.PROD.OUTLOOK.COM \
--to=ramon_fischer@hotmail.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox