| 1 |
Hello Zac, |
| 2 |
|
| 3 |
Thanks for your answer! |
| 4 |
|
| 5 |
Sorry for my questions about mailing list activity, but it was my first |
| 6 |
messages. I'm glad to know I can find portage team here. |
| 7 |
|
| 8 |
Thank you very much for your time and work in the best distro ever made! |
| 9 |
|
| 10 |
:) |
| 11 |
|
| 12 |
|
| 13 |
On 09/19/2017 12:30 AM, Zac Medico wrote: |
| 14 |
> On 09/18/2017 04:17 PM, Samuel Bernardo wrote: |
| 15 |
>> Hello, |
| 16 |
>> |
| 17 |
>> Is this mailing list alive? |
| 18 |
>> |
| 19 |
>> Should I place questions about portage and ebuild development in another |
| 20 |
>> mailing list? |
| 21 |
> This is the correct list, we're just really busy. |
| 22 |
> |
| 23 |
>> Best, |
| 24 |
>> |
| 25 |
>> Samuel |
| 26 |
>> |
| 27 |
>> |
| 28 |
>> On 09/12/2017 09:45 PM, Samuel Bernardo wrote: |
| 29 |
>>> Hello again, |
| 30 |
>>> |
| 31 |
>>> About the ebuild code check, the only script that I need to patch is |
| 32 |
>>> ebuild command right? |
| 33 |
>>> |
| 34 |
>>> A prefer not to install portage-9999 and only apply a patch to the |
| 35 |
>>> current stable version of the portage. |
| 36 |
> You can create a /etc/portage/patches/sys-apps/portage directory any |
| 37 |
> patches you place in that directory will be applied by the epatch_user |
| 38 |
> call in distutils-r1.eclass. |
| 39 |
> |
| 40 |
>>> I also realized that portage releases are available from |
| 41 |
>>> https://dev.gentoo.org/~dolsen/releases/portage/ and that releases on |
| 42 |
>>> https://anongit.gentoo.org/git/proj/portage.git don't have the tags in |
| 43 |
>>> accordance to the current release (2.3.6). I search the tags in git |
| 44 |
>>> repository for v2.3.6 and I coudn't find it (v2.3.0_rc1). |
| 45 |
> This is the tag for the portage-2.3.8 (latest) release: |
| 46 |
> |
| 47 |
> https://gitweb.gentoo.org/proj/portage.git/tag/?h=portage-2.3.8 |
| 48 |
> |
| 49 |
>>> So is release cycle in the repository different from the releases |
| 50 |
>>> available in dev.gentoo.org? |
| 51 |
>>> |
| 52 |
>>> How are you managing the releases delivery? |
| 53 |
>>> |
| 54 |
>>> I'm interested to follow the portage future updates and have the ebuild |
| 55 |
>>> development updated for the next release. |
| 56 |
> There's tarball available for the latest release here: |
| 57 |
> |
| 58 |
> https://dev.gentoo.org/~zmedico/portage/archives/portage-2.3.8.tar.bz2 |
| 59 |
> |
| 60 |
> |
| 61 |
>>> Cheers :) |
| 62 |
>>> |
| 63 |
>>> |
| 64 |
>>> On 09/12/2017 09:18 PM, Samuel Bernardo wrote: |
| 65 |
>>>> Hi Michał, |
| 66 |
>>>> |
| 67 |
>>>> On 09/12/2017 06:29 PM, Michał Górny wrote: |
| 68 |
>>>>> W dniu wto, 12.09.2017 o godzinie 17∶33 +0100, użytkownik Samuel |
| 69 |
>>>>> Bernardo napisał: |
| 70 |
>>>>>> Hi, |
| 71 |
>>>>>> |
| 72 |
>>>>>> How can I test my overlay ebuilds using the new portage EAPI that is |
| 73 |
>>>>>> only available on gentoo-portage-dev ml? |
| 74 |
>>>>>> |
| 75 |
>>>>>> I don't know where is gentoo-portage-dev... Is it a gentoo portage tree |
| 76 |
>>>>>> available from git or some url for syncing? |
| 77 |
>>>>>> |
| 78 |
>>>>> I don't really understand what you're asking for. Is it about |
| 79 |
>>>>> the failures with commands in global scope? If it's that, then it's |
| 80 |
>>>>> already merged and available via =sys-apps/portage-9999. |
| 81 |
>>>>> |
| 82 |
>>>> Yes is that I was looking for... |
| 83 |
>>>> But also didn't understand the meaning of "a patch in gentoo-portage-dev |
| 84 |
>>>> ml"... What does this stand for? |
| 85 |
>>>> |
| 86 |
>>>> Thanks for your help |
| 87 |
>> |
| 88 |
> |
Archives