Re: [gentoo-project] Setting a consistent vocabulary for ebuild-related stuff

[Brian Dolbec]

On Fri, 10 Apr 2015 15:28:06 +0200
Michał Górny <mgorny@g.o> wrote:

> Hello, developers.
>
> Since Gentoo is quite an aging technical community, a lot of wording
> has accumulated to describe various ebuild-related aspects, some of it
> rather confusing and/or outdated. Therefore, I would like to suggest
> that we establish some 'proper' vocabulary for use in official
> documentation, and deprecate some of the outdated concepts.
>
> This is meant to serve two goals particularly:
>
> 1. Reduce user/developer confusion. In particular, the long-time
> confusing two uses of 'Portage', but also working towards vocabulary
> consistent with other tools and distributions.
>
> 2. Put more emphasis on flexibility of Gentoo -- which I believe
> should be advertised as its major advantage.
>
>
> Now what I suggest:
>
> A. Portage vs the package manager
> ---------------------------------
>
> I don't know many distributions that officially support more than one
> distinct package manager. Even some of the Gentoo derivatives (e.g.
> Funtoo) don't do that. As I see it, we should be proud of that.
>
> For this reason, the official docs should treat Portage
> as the reference package manager rather than the only package manager.
> That is:
>
> - use 'the package manager' whenever the relevant action or
> information can be applied to any Gentoo package manager conforming
> to the PMS,
>
> - use 'Portage' whenever the relevant information applies purely to
>   Portage the package manager.
>
>
> B. Ebuild vs package
> --------------------
>
> 'Ebuild' is the script. If you say 'install an ebuild', that ends up
> a bit confusing. Also note that a binary package is not an 'ebuild',
> yet it is roughly equivalent to one. So:
>
> - use 'ebuild' when referring directly to the .ebuild file,
>
> - use 'package' whenever referring to the generic magic thing that
>   results of combining ebuild with eclasses, profiles and other stuff.
>
> So: 'send me the ebuild' but 'install the package'.
>
>
> C. Repository vs tree vs overlay vs Portage...
> ----------------------------------------------
>
> This one is harsh since it has a lot of historic context. Long story
> short, none of the Gentoo package managers work in pure 'overlay'
> logic anymore, so best to stop using that term. Also, better to leave
> 'trees' to the forests.
>
> And finally, Portage is the package manager and let's leave it at
> that. No need to cause users to confuse developers even further.
>
> Therefore:
>
> - Don't use 'Portage', 'tree', 'overlay' or any other thing. Just call
>   it a 'repository' (or 'ebuild repository', if you want to be more
>   specific and distinguish it from 'binary package repository').
>
> - When referring to the main Gentoo repository, call it the 'Gentoo
>   repository'. That's how it is named these days (read repo_name!),
>   and that's the least confusing name you can use.
>
> - When referring to other repositories, you can call them 'third-party
>   repositories' or alike. No point in calling them 'overlays' since
>   they are not laid over anything anymore.
>
> This is a great step towards decentralization and a good emphasis on
> the fact that Gentoo is flexible and can work with many different
> repositories.
>
>
> Your thoughts?
>

Works for me :)

-- 
Brian Dolbec <dolsen>