Re: [gentoo-portage-dev] Portage patch now on gentoo-portage-dev ml
Hello Zac, Thanks for your answer! Sorry for my questions about mailing list activity, but it was my first messages. I'm glad to know I can find portage team here. Thank you very much for your time and work in the best distro ever made! :) On 09/19/2017 12:30 AM, Zac Medico wrote: > On 09/18/2017 04:17 PM, Samuel Bernardo wrote: >> Hello, >> >> Is this mailing list alive? >> >> Should I place questions about portage and ebuild development in another >> mailing list? > This is the correct list, we're just really busy. > >> Best, >> >> Samuel >> >> >> On 09/12/2017 09:45 PM, Samuel Bernardo wrote: >>> 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- and only apply a patch to the >>> current stable version of the portage. > You can create a /etc/portage/patches/sys-apps/portage directory any > patches you place in that directory will be applied by the epatch_user > call in distutils-r1.eclass. > >>> 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). > This is the tag for the portage-2.3.8 (latest) release: > > https://gitweb.gentoo.org/proj/portage.git/tag/?h=portage-2.3.8 > >>> 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. > There's tarball available for the latest release here: > > https://dev.gentoo.org/~zmedico/portage/archives/portage-2.3.8.tar.bz2 > > >>> 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-. > 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 >> >
Re: [gentoo-portage-dev] Portage patch now on gentoo-portage-dev ml
On 09/18/2017 04:17 PM, Samuel Bernardo wrote: > Hello, > > Is this mailing list alive? > > Should I place questions about portage and ebuild development in another > mailing list? This is the correct list, we're just really busy. > > Best, > > Samuel > > > On 09/12/2017 09:45 PM, Samuel Bernardo wrote: >> 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- and only apply a patch to the >> current stable version of the portage. You can create a /etc/portage/patches/sys-apps/portage directory any patches you place in that directory will be applied by the epatch_user call in distutils-r1.eclass. >> 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). This is the tag for the portage-2.3.8 (latest) release: https://gitweb.gentoo.org/proj/portage.git/tag/?h=portage-2.3.8 >> 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. There's tarball available for the latest release here: https://dev.gentoo.org/~zmedico/portage/archives/portage-2.3.8.tar.bz2 >> 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-. >>> 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 > > -- Thanks, Zac
Re: [gentoo-portage-dev] Portage patch now on gentoo-portage-dev ml
Hello, Is this mailing list alive? Should I place questions about portage and ebuild development in another mailing list? Best, Samuel On 09/12/2017 09:45 PM, Samuel Bernardo wrote: > 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- 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-. >>> >> 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
