Hi again,

As a suggestion, I would propose for each overlay to override the eclass
functions for those necessary to EAPI 6 within their ebuilds.

For instance, go-overlay could use old eclasses that support EAPI 6
overriding the current ones. For some reason they updated their eclasses
to  EAPI 7 before updating the ebuilds.

This brings me to the main issue that is the portage cache and possible
conficts between those eclass defined in the overlay and those from
gentoo main stream. Maybe a name convention would be useful here for
future upgrades as a code styling guide for gentoo developers.

What do you think about this kind of issues?

Best,

Samuel

On 12/03/2020 10.42, Samuel Bernardo wrote:
> Hi,
>
> Is there any way to allow EAPI 6 for some overlays with current portage
> stable version (2.3.89-r1)?
>
> There are many previous functions that were updated strictly to EAPI 7.
> As an example here is the result when running "eix-sync -a":
>
>> ebuild failed with status
>> 1                                                                            
>>                                                                              
>>                                                                              
>>             
>>  
>>      Reading category 127|190 ( 66):
>> net-misc...                                                                  
>>                                                                              
>>                                                                              
>>  
>>  
>> cannot properly execute
>> /var/lib/layman/go-overlay/net-misc/dbxcli/dbxcli-1.4.0.ebuild
>>      Reading category 127|190 ( 66): net-misc... * ERROR:
>> net-misc/gnatsd-0.9.4::go-overlay failed (depend
>> phase):                     
>>  *   golang-common: EAPI=6 is not
>> supported                                                                    
>>                       
>>  
>>  *                                                        
>>  * Call
>> stack:                                                                       
>>                                                 
>>  
>>  *              ebuild.sh, line 609:  Called source
>> '/var/lib/layman/go-overlay/net-misc/gnatsd/gnatsd-0.9.4.ebuild'
>>  *    gnatsd-0.9.4.ebuild, line  10:  Called inherit
>> 'golang-single'                                                              
>>    
>>  
>>  *              ebuild.sh, line 314:  Called __qa_source
>> '/var/lib/layman/go-overlay/eclass/golang-single.eclass'
>>  *              ebuild.sh, line 112:  Called source
>> '/var/lib/layman/go-overlay/eclass/golang-single.eclass'                     
>>     
>>  
>>  *   golang-single.eclass, line  66:  Called inherit
>> 'golang-common'                                                  
>>  *              ebuild.sh, line 314:  Called __qa_source
>> '/var/lib/layman/go-overlay/eclass/golang-common.eclass'
>>  *              ebuild.sh, line 112:  Called source
>> '/var/lib/layman/go-overlay/eclass/golang-common.eclass'     
>>  *   golang-common.eclass, line  37:  Called
>> die                                                                          
>>            
>>  
>>  * The specific snippet of
>> code:                                                                        
>>                              
>>  
>>  *              die "${ECLASS}: EAPI=${EAPI:-0} is not supported"
>> ;;                                             
>>  *                                                                           
>>                                                         
>>  
>>  * If you need support, post the output of `emerge --info
>> '=net-misc/gnatsd-0.9.4::go-overlay'`,                                     
>>  
>>  * the complete build log and the output of `emerge -pqv
>> '=net-misc/gnatsd-0.9.4::go-overlay'`.                                      
>>  
>>  * Working directory:
>> '/usr/lib64/python3.6/site-packages'                                         
>>                                   
>>  
>>  * S: '/gnatsd-0.9.4'
> Thanks in advance for your help, comments and suggestions.
>
> Best,
>
> Samuel
>

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to