Hello Marc! Just a small reminder... What I was proposing was a text file with a bunch of entries like this:
URL=https://dettus.net/dMagnetic/sixel_mag_jinxter.png SHA256=1bb9fc3e1b0878c3d9afc8e7c35c62e848ec6e1d52f179c915282b2d8ad82bf2 PERMIT_WEBSITE=yes You mentioned another aspect which I have overlooked: CURATION. Please see my answers inline... > Marc Espie <[email protected]> hat am 21.06.2022 18:17 CEST geschrieben: > with RCS proper, because it *will* mangle binary files unless you do > things correctly. Please do not put screenshots under RCS control. If you were going to mirror all of the screenshots, using the same policy as the source.tar.gz files might be a better approach. > I believe that, if you want to supplement ports-readmes-dancer (for instance) I was not aware of ports-readmes-dancer, I will google it later. Thanks! > That's most probably the least error-prone way to do things. "least error-prone way" is my favourite kind of way. :) > The thing you could possibly do is start creating a simple table > fullpkgpath - screenshot url(s) My original mail, the one with which I opened this thread, already had a file like that in its attachement. It was meant as an example. If the attachement did not survive the way to the mailing list, then I suppose I could sent it as an inline again? Or was the file not what you had in mind? Thomas
