From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh
Date: Thu, 7 Jan 2021 08:51:40 +0000 [thread overview]
Message-ID: <20210107085140.2d76cc73@digimed.co.uk> (raw)
In-Reply-To: <20210107084300.u4tcsunmev5n7cpz@fedora.osfans.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Thu, 7 Jan 2021 16:43:00 +0800, Kevin Shell wrote:
> What's the relationship between
> ebuild(1) & emerge(1), ebuild(1) & ebuild.sh?
emerge is the high level command normally used by users to manage
packages. ebuild is only used for installing and removing packages,
emerge does a lot more besides, and is a more low level command.
ebuild.sh is for use by portage, bit by users.
> Why the ebuild(1)(python script) command exists,
> is it for debugging ebuild scripts?
That is one of its main uses, it can also be used to hack the ebuild
process.
--
Neil Bothwick
Most software is about as user-friendly as a cornered rat!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-07 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 8:43 [gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh Kevin Shell
2021-01-07 8:51 ` Neil Bothwick [this message]
2021-01-07 9:07 ` Kevin Shell
2021-01-07 10:26 ` Neil Bothwick
2021-01-07 12:28 ` tastytea
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=20210107085140.2d76cc73@digimed.co.uk \
--to=neil@digimed.co.uk \
--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