| 1 |
On Fri, Nov 25, 2022 at 02:28:23PM +0100, Volkmar W. Pogatzki wrote: |
| 2 |
> > Michał Górny <mgorny@g.o> hat am 25.11.2022 14:16 CET geschrieben: |
| 3 |
> > |
| 4 |
> > |
| 5 |
> > On Fri, 2022-11-25 at 10:04 +0100, Volkmar W. Pogatzki wrote: |
| 6 |
> > > > This doesn't seem consistent. How is it supposed to work? |
| 7 |
> > |
| 8 |
> > You didn't answer this question. |
| 9 |
> |
| 10 |
> Sorry. I have to admit I have no idea how remote-id works and what's |
| 11 |
> needed to make a new remote-id work. |
| 12 |
|
| 13 |
The problem from the examples you gave is log4j-core: |
| 14 |
|
| 15 |
dev-java/log4j-core -> https://logging.apache.org/log4j/2.x/ |
| 16 |
dev-java/pdfbox -> https://pdfbox.apache.org/ |
| 17 |
net-libs/serf -> https://serf.apache.org/ |
| 18 |
|
| 19 |
you can have e.g. |
| 20 |
url-template: https://<remote-id>.apache.org/ |
| 21 |
metadata: <remote-id type="apache">logging</remote-id> |
| 22 |
-> https://logging.apache.org/ |
| 23 |
|
| 24 |
But that won't add a log4j/2.x at the end of the url, current |
| 25 |
implementation just does a dumb replacement for a single part |
| 26 |
|
| 27 |
-- |
| 28 |
ionen |
Archives