List patches in repology dump #226
Comments
|
So you could easily update the Ravenports parser to accommodate building
logs.
The DragonFly logs are publicly accessible:
https://loki.dragonflybsd.org/raven/logs/
Format is "<namebase>___<standard>.log" e.g. GraphicsMagick___standard.log
The drawback is if the package does not build on DragonFly and is marked as
such (e.g. Linux or FreeBSD only) then the link would be broken since the
log wouldn't exist.
John
…On Thu, Mar 18, 2021 at 9:31 PM Dmitry Marakasov ***@***.***> wrote:
Repology now supports extracting information on patches from repositories
which make it available, with intent to provide aggregated list of patches
to upstream and maintainers. If possible, it would be nice to have a list
of patches in ravenports 'repology.json. The expected format would be a
list of paths relative to the port directory (or to patches/ if they always
reside there).
Package building logs are now supported too. Not sure if binary packages
are built for ravenports, but if logs are available these could be of use
too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#226>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAISZ5RNPXUSGI3E5VAOO6TTEKZONANCNFSM4ZN45PAA>
.
|
|
Log links added, thanks!
That's fine, there's linkchecker which would mark missing logs. |
|
I'll just point out that currently you're only supporting a single variant.
for example, https://repology.org/project/git/information
On ravenports git has 2 variants: standard and lite.
Only the "standard" variant log is displayed when there are 2 possibilities.
Just FYI
…On Wed, Mar 24, 2021 at 3:53 PM Dmitry Marakasov ***@***.***> wrote:
Log links added, thanks!
then the link would be broken since the log wouldn't exist
That's fine, there's linkchecker which would mark missing logs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAISZ5WXKDI6CVBCCQRCUSDTFJGLFANCNFSM4ZN45PAA>
.
|
|
Repology currently only processed single variant. Will process all of them at some point, which would lead to gathering all the logs. |
I missed this before. That's a great idea. But is this actually happening? |
Yes, https://repology.org/project/firefox/information#Patches
No. |
|
oh I see. it's up to upstream to check existing patches on the repology page (so passive notification rather than active). |
Repology now supports extracting information on patches from repositories which make it available, with intent to provide aggregated list of patches to upstream and maintainers. If possible, it would be nice to have a list of patches in ravenports '
repology.json. The expected format would be a list of paths relative to the port directory (or to patches/ if they always reside there).Package building logs are now supported too. Not sure if binary packages are built for ravenports, but if logs are available these could be of use too.
The text was updated successfully, but these errors were encountered: