678016 – ebuild(1) lists phase functions (as arguments to the ebuild command) in the wrong order

Bug 678016 - ebuild(1) lists phase functions (as arguments to the ebuild command) in the wrong order

Summary: ebuild(1) lists phase functions (as arguments to the ebuild command) in the w...

Status:	UNCONFIRMED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Documentation (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2019-02-14 17:45 UTC by 3uklz9+cwyw433xfnykw
Modified:	2019-02-14 21:27 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description 3uklz9+cwyw433xfnykw 2019-02-14 17:45:59 UTC

The manual page for ebuild lists the functions in wrong order.

It should list them in the same order portage executes them.

In particular, man page has preinst before install.

According to https://devmanual.gentoo.org/ebuild-writing/functions/index.html, install runs before preinst.

The man page does not explicitly say that functions are listed in order, but it claims that 'portage will execute all the functions in order up to the one actually specified', without saying what 'the order' actually is. Therefore a reader may assume that they are listed in order.