StaticSrcUri: handle more cases#453
Conversation
Codecov ReportBase: 95.97% // Head: 81.22% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #453 +/- ##
===========================================
- Coverage 95.97% 81.22% -14.75%
===========================================
Files 55 55
Lines 7824 7846 +22
Branches 2225 2234 +9
===========================================
- Hits 7509 6373 -1136
- Misses 194 1375 +1181
+ Partials 121 98 -23
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Perhaps deduplicate this to report every (pkg, match) occurence once? |
For extra kudos, perhaps you could special case removing all separators using the same character into |
|
Added the following replacements:
Updated results for Gentoo tree are in the first comment. No result suggesting |
thesamesam
left a comment
There was a problem hiding this comment.
LGTM although worried about coverage, surely it's wrong?
- handle various new cases, and a little less permissive regex - add cases of usage of `ver_rs` and `ver_cut` - suggest the user with replacement Resolves: pkgcore#450 Resolves: pkgcore#451 Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
f30b44e to
6d8282f
Compare
Thanks. Yes, the coverage is wrong, because of multiple force-pushes by me at the beginning. |
ver_rsandver_cutThe new logic:
/orPN[-._]?- I don't want random suggestion because it somehow matches somewhere in commit id.[v]?${P}${PV}$(ver_cut 1-n)wheren> 1 - I skip the variant of$(ver_cut 1)because of large amount of false positives$(ver_rs 1-n '#')wheren> 0 and#is one ofƐ(empty str),_,-. Can add other symbols.Sadly, the code for generating the regex became an abomination.
new StaticSrcUri results on gentoo tree (v2)
Resolves: #450, #451