Re: [gentoo-portage-dev] Portage patch now on gentoo-portage-dev ml

[Samuel Bernardo]

Hello again,

About the ebuild code check, the only script that I need to patch is
ebuild command right?

A prefer not to install portage-9999 and only apply a patch to the
current stable version of the portage.

I also realized that portage releases are available from
https://dev.gentoo.org/~dolsen/releases/portage/ and that releases on
https://anongit.gentoo.org/git/proj/portage.git don't have the tags in
accordance to the current release (2.3.6). I search the tags in git
repository for v2.3.6 and I coudn't find it (v2.3.0_rc1).

So is release cycle in the repository different from the releases
available in dev.gentoo.org?

How are you managing the releases delivery?

I'm interested to follow the portage future updates and have the ebuild
development updated for the next release.

Cheers :)


On 09/12/2017 09:18 PM, Samuel Bernardo wrote:
> Hi Michał,
>
> On 09/12/2017 06:29 PM, Michał Górny wrote:
>> W dniu wto, 12.09.2017 o godzinie 17∶33 +0100, użytkownik Samuel
>> Bernardo napisał:
>>> Hi,
>>>
>>> How can I test my overlay ebuilds using the new portage EAPI that is
>>> only available on gentoo-portage-dev ml?
>>>
>>> I don't know where is gentoo-portage-dev... Is it a gentoo portage tree
>>> available from git or some url for syncing?
>>>
>> I don't really understand what you're asking for. Is it about
>> the failures with commands in global scope? If it's that, then it's
>> already merged and available via =sys-apps/portage-9999.
>>
> Yes is that I was looking for...
> But also didn't understand the meaning of "a patch in gentoo-portage-dev
> ml"... What does this stand for?
>
> Thanks for your help