Opened 7 years ago
Closed 7 years ago
#17365 closed defect (wontfix)
please use explicit revision numbers in externals
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description
Hi,
I'm trying to package JOSM for my distribution, which requires getting the source code and compiling it. Obviously we want to make sure we get the right source code, so there is a checksum so any developper can make sure they have the right sources. Unfortunately, the result of "svn co" (with the latest "stable" revision) is not deterministic as externals can be updated and change the result of the command.
It's also a problem, since it makes it impossible to download the source code that was used to build a certain binary version of JOSM.
Would you consider using explicit revision numbers for externals, as advised by most tutorials/documentation about svn, or at least publish a snapshot of the sources that were used to build JOSM, for every release (I mean, a tarball containing the content of the repository at the time JOSM was built, not "sources" in the maven sense)?
Thank you!



We're switching to git but it will take some time, see #16857 #16858 #16871 #16944 for details.