From: tastytea <tastytea+gentoo@tastytea.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ebuild: How to deal with external repositories properly (best practise)?
Date: Tue, 28 Jul 2020 10:53:40 +0200 [thread overview]
Message-ID: <20200728105340.4239f30d@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <AM6P191MB0296A527C75224E0013F9954EF730@AM6P191MB0296.EURP191.PROD.OUTLOOK.COM>
On 2020-07-28 06:47+0200 Ramon Fischer <Ramon_Fischer@hotmail.de> wrote:
> […]
> The thing I am concerned about, is, that I am pulling something from
> an external source, which I am installing on my system and giving it
> root privileges[4].
>
> The only best practise I can think of, is, to fork the external
> repository, linking the ebuild to my fork and updating it on demand,
> so I have full control over it.
>
> Would this be the way to do it?
You can mask all packages from a repository in
/etc/portage/package.mask/ with
*/*::repo-name
and unmask the packages you want in /etc/portage/package.unmask/ with
x11-misc/drm_master_util::repo-name
or just the version you want with
=x11-misc/drm_master_util-9999::repo-name
.
The maintainer of the repo could still replace the ebuild with a
malware installer.
next prev parent reply other threads:[~2020-07-28 8:53 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 [this message]
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 ` [SOLVED] " Ramon Fischer
2020-08-04 22:57 ` 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=20200728105340.4239f30d@ventiloplattform.tastytea.de \
--to=tastytea+gentoo@tastytea.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