LDraw.org Discussion Forums

These files (linked here https://www.ldraw.org/part-updates):
* https://www.ldraw.org/library/updates/complete.zip
* https://www.ldraw.org/library/official/LDConfig.ldr

are being periodically replaced with new versions. This breaks all ports that store cryptographic fingerprints, because they see that these files periodically change and ports fail to build.

For example, the FreeBSD port cad/ldraw would break with every new release of complete.zip and LDConfig.ldr

Could you please add a date of release to these filenames, for example make these URLs look like this:
* https://www.ldraw.org/library/updates/co...201229.zip
* https://www.ldraw.org/library/official/L...201229.ldr


Thank you,
Yuri

Adding a date to LDConfig.ldr will break all software that makes use of it. Adding a date to complete.zip probably won't break anything as long as ptreleases.cgi continues to only include the latest complete update in its list.

(2021-06-08, 1:19)yurivict Wrote: [ -> ]These files (linked here https://www.ldraw.org/part-updates):
* https://www.ldraw.org/library/updates/complete.zip
* https://www.ldraw.org/library/official/LDConfig.ldr

are being periodically replaced with new versions. This breaks all ports that store cryptographic fingerprints, because they see that these files periodically change and ports fail to build.

For example, the FreeBSD port cad/ldraw would break with every new release of complete.zip and LDConfig.ldr

Could you please add a date of release to these filenames, for example make these URLs look like this:
* https://www.ldraw.org/library/updates/co...201229.zip
* https://www.ldraw.org/library/official/L...201229.ldr


Thank you,
Yuri

I don't see this happening. The release software is custom written and changing it can be precarious. That said, I might be able to add a hash of the zip to the download page for paranoid people to check against.

(2021-06-10, 3:00)Orion Pobursky Wrote: [ -> ]I don't see this happening. The release software is custom written and changing it can be precarious. That said, I might be able to add a hash of the zip to the download page for paranoid people to check against.

Why don't you just add a symlink?

It would only need a small post operation on top of the normal release procedure, namely:

copy the new complete.zip to something like 20210610-complete.zip and then symlink complete.zip to it.
On the next release you do the same but the old zip will remain.

The packages need to pull the 20210610-complete.zip variant during building, not sure how they (automatically) would know which one is currently the newest though. Mayby a small info file like "https://www.ldraw.org/library/releaseInfo.txt"

my 2cts

(2021-06-10, 19:49)Roland Melkert Wrote: [ -> ]Why don't you just add a symlink?

It would only need a small post operation on top of the normal release procedure, namely:

copy the new complete.zip to something like 20210610-complete.zip and then symlink complete.zip to it.
On the next release you do the same but the old zip will remain.

The packages need to pull the 20210610-complete.zip variant during building, not sure how they (automatically) would know which one is currently the newest though. Mayby a small info file like "https://www.ldraw.org/library/releaseInfo.txt"

my 2cts

Maybe when we start planning the software to replace the Parts Tracker but not until then.