On 12/11/24 15:08, Michał Górny wrote:
you can quickly update
hundreds of bugs filed against it
Does it need to be added to the list of exceptions [1] or is it
considered as a manual, i.e. non-automated, script?
Cheers,
APN
[1] https://bugs.gentoo.org/bots.html
On 10/17/24 19:32, Desarrollos WEB wrote:
I see a very interesting utility to automate the process of updating and
searching for new software versions. Livecheck can be extended to notify
maintainers, upload pull requests, create ebuild tar.gz with go-module,
etc.., thus eliminating much of t
On 9/17/23 20:28, Florian Schmaus wrote:
sounds perfectly fine.
Ideally I'd not limit it to only doi but also arxiv, zenodo, inspirehep.
They can all be referenced by https://... . I agree a specific type is
kind of unnecessary. However, the same paper can be referenced by all of
them.
Thanks. Instead of using the lang entry I can imagine these other
approaches:
1. doi/arxiv/... links could also easily be plugged in custom upstream
remote ids, but that also feels a bit wrong since all other [upstream
remote
ids](https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Upstrea
Dear Larry,
I am looking for a way to link scientific publications to
ebuilds/packages. The easiest, but hacky way right now is to use the
|https://doi.org/...|. Integration with
|epkginfo|/|equery meta| works nicely out of the box. However, currently
|pkgcheck| and/or the XML format complain
