Hi
There is a Packages component at
https://bugs.gentoo.org/enter_bug.cgi?product=Websites for reports
like this

пт, 12 февр. 2021 г. в 07:10, Jaco Kroon <j...@uls.co.za>:

>
> Hi,
>
> Firstly:  I was aware of packages.gentoo.org - but only really discovered it 
> in the week - THANK YOU VERY MUCH FOR THIS.
>
> Not sure whether this is the best place for my request, so if not, please 
> feel free to bat me in the right direction.
>
> https://packages.gentoo.org/packages/net-misc/asterisk (example) refers.
>
> I'm the (proxy) maintainer.
>
> The above URL merely states:
>
> It seems that version 18.2.0 is available upstream, while the latest version 
> in the Gentoo tree is 16.15.1.
>
> This is correct.  Just looking a little down, it's noted there are two 
> versions currently in tree:
>
> 16.15.1-r2 : 0
> 13.38.1-r2 : 0
>
> What's not indicated, there are subslots (13 and 16 respectively).
>
> eshowkw (app-portage/gentoolkit) shows:
>
> Keywords for net-misc/asterisk:
>               |                             |   u      |
>               | a   a     p s     a   r     |   n      |
>               | m   r h   p p   s l i i m m | e u s    | r
>               | d a m p p c a x 3 p a s 6 i | a s l    | e
>               | 6 r 6 p p 6 r 8 9 h 6 c 8 p | p e o    | p
>               | 4 m 4 a c 4 c 6 0 a 4 v k s | i d t    | o
> --------------+-----------------------------+----------+-------
>    13.38.1-r2 | + ~ ~ o ~ ~ o + o o o o o o | 7 o 0/13 | gentoo
> --------------+-----------------------------+----------+-------
> [I]16.15.1-r2 | ~ ~ ~ o ~ ~ o ~ o o o o o o | 7 o 0/16 | gentoo
>
> Which is currently as intended (yea, I'm behind the times - stable and 
> working in this case over bleeding edge - and nobody other than me is yet 
> pushing me to stable /16, although I have a bug request to package 18 which I 
> intend to start work on today hopefully since I'm working on asterisk stuff 
> for business purposes today anyway).
>
> 13 is security only release now, and 16 and 18 are the primary branches where 
> 16 is more intended as stable and more fluctuations on 18 still (which 
> precludes me from using it for our company just yet).
>
> Point being, it would be great if packages.gentoo.org could indicate that in 
> above cases as follows:
>
> 18.2.0 is available, which is correct, and desired, but if it could also 
> indicate that for the 16 branch there is currently a version of 16.16.0 
> available, and for 13 things are up to date.
>
> Would be useful too to indicate that certain branches (eg, 17 in the asterisk 
> case will not be packaged due to being primarily development branches, or at 
> the very least, will not be considered for stabling)
>
> In other words, guessing I'm looking for some form of "branched versions" 
> support here.
>
> I know security already has some work around subslots as it was the sec team 
> that requested me to add subslots to net-misc/asterisk.
>
> And yes ... looks like repology does have a few issues around branches too:  
> https://repology.org/project/asterisk/cves?version=13.38.1
>
> So I would completely understand if it's not possible to deal with this.  As 
> per 
> https://archives.gentoo.org/gentoo-dev/message/b793f4da5a5b5e20a063ea431500a820
>  there are certain configs that can go into 
> https://gitweb.gentoo.org/sites/soko-metadata.git/ - however, not being a 
> core developer, I don't have (nor am I requesting) access here.  May I 
> suggest that in-package metadata (ie, metadata.xml, or even inside the 
> ebuilds) might be a better location for some of this configuration if 
> possible, and if it makes sense?  For me the advantage is that as a PM I can 
> submit the required information via PR.
>
> A description of the branch structure may be more suitable here anyway, 
> because that way other tools can leverage it too?
>
> Then again, perhaps just looking at the subslots as already available is good 
> enough, in the case of the packages I work on this would indeed be adequate, 
> but it may not be for other packages.
>
> Looking at repology.org itself, I'm not sure my request is trivial, and I'm 
> not going to ask tons of effort be put into this, but perhaps an interesting 
> challenge for someone at some point.
>
> Kind Regards,
> Jaco

Reply via email to