Re: [gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers
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. If one wants to capture that redundancy. Could something like this work? zenodo='https://zenodo.org/record/8256635'/> arxiv='https://arxiv.org/pdf/2211.15838' doi='https://doi.org/10.22323/1.414.0245'/> I don't think this grouping is important though, just something useful one could add if one already goes for the GLEP route. Hence, I am not sure why you assume its too much work. If a user wants to list the references epkginfo/equery already shows the homepage or doc links, but not the new reference element, right? Similarly, the references would need extra treatment to be directly shown on packages.gentoo.org.| | Cheers, APN OpenPGP_0xCD7F8280C916D488.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: [gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers
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/Upstream_remote-id_types) are repos/source code providers. 2. Adding something specific to GLEP 68, like `type="doi"> https...`. However that seems like a bit too much work for adding something that only a small subset of users (science) cares about. Also integration of parsing with existing tools is an extra overhead. 3. Put them also into `HOMEPAGE` of the ebuilds. Again bit of a wrong place, but with the (minor) advantage of having possibly different/new references per version. Is any of these three superior/preferable? OpenPGP_0xCD7F8280C916D488.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
[gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers
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 complains about repeated |lang| entries and does not allow long |lang| attributes (i.e. |lang="inspirehep"| fails understandably). You can inspect a detailed example here https://github.com/gentoo/sci/pull/1216. The more sophisticated way, instead of abusing the |lang| attribute, would be another attribute, perhaps |reference|, or a new element in |upstream| instead of |doc|. Before I move forward with this idea, I would be curious to hear your thoughts on it. Best, APN OpenPGP_0xCD7F8280C916D488.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
