public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Neuwirth <alexander@neuwirth-informatik.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers
Date: Fri, 15 Sep 2023 11:31:24 +0200	[thread overview]
Message-ID: <e1a684e3-42e4-12e8-2fa3-a38339e3d6ad@neuwirth-informatik.de> (raw)


[-- Attachment #1.1.1.1: Type: text/plain, Size: 818 bytes --]

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 
|<doc lang="doi">https://doi.org/...</doc>|. 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


[-- Attachment #1.1.1.2: Type: text/html, Size: 1663 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 8923 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

             reply	other threads:[~2023-09-15  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  9:31 Alexander Neuwirth [this message]
2023-09-15 10:15 ` [gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers Ulrich Mueller
2023-09-17 12:18   ` Alexander Neuwirth
2023-09-17 15:18     ` Ulrich Mueller
2023-09-17 18:28     ` Florian Schmaus
2023-09-17 19:06       ` Alexander Neuwirth
2023-09-17 20:55       ` Ulrich Mueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e1a684e3-42e4-12e8-2fa3-a38339e3d6ad@neuwirth-informatik.de \
    --to=alexander@neuwirth-informatik.de \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox