[gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh

[gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh

[Kevin Shell]

Hello gentoo list.

What's the relationship between
ebuild(1) & emerge(1), ebuild(1) & ebuild.sh?

Why the ebuild(1)(python script) command exists,
is it for debugging ebuild scripts?

--
kevin

Re: [gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh

[Neil Bothwick]

[-- 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 --]

Re: [gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh

[Kevin Shell]

On Thu, Jan 07, 2021 at 08:51:40AM +0000, Neil Bothwick wrote:
> 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.
>
Is ebuild(1) meant for standalone use and not used by emerge(1)?
I know ebuild.sh is used by emerge(1).

> > 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

Thanks for reply.

--
kevin

Re: [gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Thu, 7 Jan 2021 17:07:36 +0800, Kevin Shell wrote:

> > 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.
> >  
> Is ebuild(1) meant for standalone use and not used by emerge(1)?
> I know ebuild.sh is used by emerge(1).

Yes it is, I guess that's why it has a man page and ebuild.sh doesn't.

However, in normal use of a Gentoo system, it shouldn't be needed.
However, it can come in handy if you have to abort a lengthy ebuild and
don't want to start over.


-- 
Neil Bothwick

A man needs a mistress - just to break the monogamy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Portage: emerge(1) ebuild(1) ebuild.sh

[tastytea]

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

On 2021-01-07 10:26+0000 Neil Bothwick <neil@digimed.co.uk> wrote:

> On Thu, 7 Jan 2021 17:07:36 +0800, Kevin Shell wrote:
> 
> > > 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.
> > >    
> > Is ebuild(1) meant for standalone use and not used by emerge(1)?
> > I know ebuild.sh is used by emerge(1).  
> 
> Yes it is, I guess that's why it has a man page and ebuild.sh doesn't.
> 
> However, in normal use of a Gentoo system, it shouldn't be needed.
> However, it can come in handy if you have to abort a lengthy ebuild
> and don't want to start over.

In that case I'd recommend:
    sudo FEATURES="keepwork keeptemp" emerge --resume
keepwork disables most of the clean phase.

ebuild(1) is useful for package maintainers to check if a package is
installing correctly and if the tests run successfully before pushing
it to a repository.

You could also use it to install packages that are not in a repository,
but I wouldn't recommend it.

Kind regards, tastytea

-- 
Get my PGP key with `gpg --locate-keys tastytea@tastytea.de` or at
<https://tastytea.de/tastytea.asc>.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]